Skip to main content

Timeline for Unix file naming convention

Current License: CC BY-SA 4.0

13 events
when toggle format what by license comment
S Oct 1, 2024 at 1:49 history suggested Iain4D CC BY-SA 4.0
Updated to '-l'. One really wants to count the number of lines (ls to a pipe will put one filename per line). If a file name has a space, '-w' word cound
Sep 30, 2024 at 19:53 review Suggested edits
S Oct 1, 2024 at 1:49
Mar 4, 2024 at 21:15 comment added Jack Wasey Using hyphens might be better (or worse) when writing systemd units. An hyphen becomes a forward slash when a unit name is systemd-unescaped, whereas, if you actually wanted an hyphen, it must be escaped in the file name.
Jun 21, 2020 at 14:26 comment added Ruslan A few examples of camelCase/PascalCase I found on my system: config files for GeoIP and PackageKit, config and libraries from ImageMagick, config paths for LessTif, glibc component libBrokenLocale.so.
Jun 29, 2017 at 14:21 history edited Stéphane Chazelas CC BY-SA 3.0
added 50 characters in body
Jan 24, 2017 at 5:14 comment added Wildcard +1 for the references. (@Proletariat, the ls output from /usr/bin is a reference. This is a question about conventions.)
Mar 7, 2016 at 16:21 comment added Proletariat Thanks. Do you have any references for these conventions?
Mar 4, 2016 at 17:31 comment added Mikel @Hugo Yes. The above shows minus (409) vs underscore (178).
Mar 4, 2016 at 9:26 comment added Hugo So the hyphen/minus/dash is more common that the underscore.
Nov 19, 2015 at 17:13 comment added Depado The . char can also be used to rotate things, not only to specify an extension. For example my.log my.log.1 my.log.2.gz.
Feb 13, 2011 at 22:07 history edited Mikel CC BY-SA 2.5
added 400 characters in body
Feb 13, 2011 at 21:57 history edited Mikel CC BY-SA 2.5
added 251 characters in body
Feb 13, 2011 at 21:49 history answered Mikel CC BY-SA 2.5