-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Nov 16, 2015 at 12:29:00PM -0600, David Wright wrote:
[...] > > Whereas in UNIX, a file name is just a string: very few characters are > > special: steer clear of NUL and slash. If you want to have an easy life > > with shell scripts, steer clear of whitespace. > > > > [...] > > You appear to be trying to shift the discussion to the semantics and > underlying implementation details of file extensions, and I don't know > why. I have clearly stated what I mean when I talk of "extension", > ie the same thing as what you called "ending" earlier. At this point, I think our discussion is reaching the point of diminishing returns (definitely for me, but I think for you also) -- so let's agree to differ. You do whatever you want on your box. For me, *having to* have an ending for a file is definitely a "design smell" (the authors of the Debian policy, btw, agree with me on that [1]). I'm out of this discussion. [1] <https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts> regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlZK2bYACgkQBcgs9XrR2kZbtQCfTlZkLEeD515dDuuw+1FNLFl6 PAQAn1av0QiYYnohErqiA0YXRiAJ9T2s =L/0R -----END PGP SIGNATURE-----