Mercurial > blog
changeset 163:c0487c6c9c95
Fixed grammar.
author | Oleksandr Gavenko <gavenkoa@gmail.com> |
---|---|
date | Tue, 30 Oct 2018 20:39:34 +0200 |
parents | 2f52511eaba7 |
children | 2036ab1c25bf |
files | 97c58616-ce5e-489a-9e6c-f3ba7261000b/index.rst |
diffstat | 1 files changed, 4 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/97c58616-ce5e-489a-9e6c-f3ba7261000b/index.rst Tue Oct 30 20:36:28 2018 +0200 +++ b/97c58616-ce5e-489a-9e6c-f3ba7261000b/index.rst Tue Oct 30 20:39:34 2018 +0200 @@ -6,7 +6,7 @@ :updated: 2017-02-09 :tags: fs, naming -Putting one symbol prefix from the beginning of ASCII chart to file name bring that file up in a +Putting one symbol prefix from the beginning of ASCII chart to a file name bring that file up in a list of files ordered by names. Here is the list of possible candidates:: @@ -51,8 +51,8 @@ Dot is safe as prefix in file name but solely ``.`` and ``..`` have special meaning for FS and it should be qouted in regex. -The winner is comma ``,`` although it is hard to distinguish. You may see comma as prefix in Lisp -special backquote syntax. +The winner is comma ``,`` although it is hard to distinguish from dot sign. You may see comma as +prefix in a Lisp special backquote syntax. Some tools uses comma as field separator. For example in Ant build tools this:: @@ -66,7 +66,7 @@ because ``,`` have special meaning when used in ``includes`` attribute. -Another pretty safe prefix is plus sign except that it require escaping in regex. +Another pretty safe prefix is a plus sign except that it requires escaping in regex. GNU Coreutils have utility that checks file names for safety::