From a7cc274e2fa2f4cd73ab3245ca2e38c7ffd47293 Mon Sep 17 00:00:00 2001 From: Zhiming Wang Date: Fri, 8 Jan 2016 12:29:32 -0800 Subject: Markdown source files: Revert YAML closing line from ... to --- GFM doesn't support closing with ..., and the rendered results are less than satisfactory. --- ...2015-05-19-bash-the-special-slash-character-in-filename-expansion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source/blog/2015-05-19-bash-the-special-slash-character-in-filename-expansion.md') diff --git a/source/blog/2015-05-19-bash-the-special-slash-character-in-filename-expansion.md b/source/blog/2015-05-19-bash-the-special-slash-character-in-filename-expansion.md index a3a789f9..a30c220f 100644 --- a/source/blog/2015-05-19-bash-the-special-slash-character-in-filename-expansion.md +++ b/source/blog/2015-05-19-bash-the-special-slash-character-in-filename-expansion.md @@ -2,7 +2,7 @@ title: "Bash: the special slash character in filename expansion" date: 2015-05-19T18:33:51-07:00 date_display: May 19, 2015 -... +--- It is well-known and common sense that the slash character (`/`) serves a special role in Bash filename expansion. For instance, the asterisk `*` certainly won't match `/` or `.` when used in filename expansion; otherwise, a standalone `*` would match everything in the filesystem. -- cgit v1.2.1