Sujet : Re: Rationale for aligning data on even bytes in a Unix shell file?
De : vallor (at) *nospam* cultnix.org (vallor)
Groupes : comp.lang.c comp.miscSuivi-à : comp.miscDate : 01. May 2025, 01:57:42
Autres entêtes
Message-ID : <m7fv86FrpdqU3@mid.individual.net>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
User-Agent : Pan/0.162 (Hmm4; 7b109588; Linux-6.14.4)
On Wed, 30 Apr 2025 23:56:40 -0000 (UTC), Lawrence D'Oliveiro
<
ldo@nz.invalid> wrote in <
vuudbo$1ajpm$7@dont-email.me>:
On Wed, 30 Apr 2025 12:38:53 -0000 (UTC), Muttley wrote:
Its certainly not a scheme I'd use, but I've also seen Makefile and
makefile in the same package build directory in the past.
The GNU “make” command, specified without a filename, looks for
“GNUmakefile”, then “Makefile”, then “makefile”. The man page
<https://manpages.debian.org/make(1)> says:
We recommend Makefile because it appears prominently near the
beginning of a directory listing, right near other important files
such as README.
But is this still true for most people? I think the default sort
settings these days no longer put all-caps names at the top.
(Setting x-post and followups to comp.misc -- follow or ignore,
it's up to you...)
On Linux, try:
LC_COLLATE=C ls -l
...and the capitalized filenames will float to the top.
(Discovered by logging into my Panix shell and inspecting
the behavior and settings there.)
-- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti OS: Linux 6.14.4 Release: Mint 22.1 Mem: 258G