Re:SharpScript
by soapdog on Monday August 19, 2019 @12:57PM
(#20739447)
if the author is reading, be aware that `.ss` is used by a lot of Scheme implementations.
[ Parent
| on HN ]
He should have used '.sh'
Re:SharpScript
by WorldMaker on Monday August 19, 2019 @03:12PM
(#20740817)
Or the actual Sharp symbol. The plain octothorpe (#) is reserved and unavailable for filenames, but most Unicode-capable file systems should be fine with the Sharp symbol, and I'm sure that wouldn't be confusing at all
http://www.fileformat.info/info/unicode/char/266f/index.htm
ETA: Of course HN's own Unicode eater doesn't like the Sharp symbol in posts.
.sh is for shell scripts which is the only time where #Script stand-alone .ss scripts are used, overloading .sh would confuse what’s a Bash Script or a #Script Script, which are completely different.
‘.ss’ is the most obvious ext for “SharpScript”, but that only applies for stand-alone scripts where you can also use .html extension since most of time it’s used as a template language inside HTML pages that’s embedded inside a .NET/Core App to provide dynamic scripting, in which case ‘.ss’ is never used.
When are we going to open up to `.s#`
Re:SharpScript
by WorldMaker on Monday August 19, 2019 @03:15PM
(#20740842)
The basic `#` is a reserved character in most shells (for comments, typically), and reserved in both POSIX file naming and Windows file naming conventions.
The similar looking Unicode Sharp, however is available.
FWIW, in bash you can "vim hello.s#" without issue (for # to be a comment, it must be preceded by whitespace).
Re:SharpScript
by benbristow on Monday August 19, 2019 @01:45PM
(#20739927)
Could use 'sscr' perhaps? (although close to scr for screensaver files)