Hi Graham!
On Fr, 15 Jul 2016, Graham Nicholls wrote:
> @Richard Mitchell.
>
> I can't tell you how much I object to this. (I'm not being aggressive,
> honest!)
>
> There is no "proper extension" for a shell script. Run "file /usr/bin/* |
> grep -i shell" to see a list of o/s built in shell scripts. Then run this:
> file /usr/bin/* | grep -i shell | awk '$1 ~ /\.sh/'
> This is a (silly) windowsism, where file-extensions matter. Now, Unix
> does sometimes care. The C compiler, for instance expects source in .c and
> headers in .h. But, or course it produces executables with no .exe
> extension. For a shell script, it's the #! line which tells the kernel to
> run it in a shell, and magic numbers for other types (which is all the same
> thing, and how "file" works).
This is true, but using a "proper extension" still is a convention, that
help the user expect certain things and also makes sure, other programs
can guess the filetype easily.
> Sorry to rant, but it's important to me - and you might guess where I stand
> on systemd :-)
While we are at the ranting, can you please make sure, to actually reply
to the correct message and not to the message digest and delete those
long quotes, that do not matter please. Thanks.
Best,
Christian
--
Wer keiner Fliege etwas zuleide tut, kann auch keine Krawatte binden.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment