From 6458fe2de26e181178cf47c026ce989eed815dd1 Mon Sep 17 00:00:00 2001 From: Zhiming Wang Date: Mon, 21 Sep 2015 14:44:38 -0700 Subject: pyblog: date-display => date_display, and update posts Looks slightly more professional. --- ...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 7e6c6e3a..143a5f36 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 @@ -1,7 +1,7 @@ --- title: "Bash: the special slash character in filename expansion" date: 2015-05-19T18:33:51-07:00 -date-display: May 19, 2015 +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