Replies: 13 comments 2 replies
-
I think sometimes Ruby uses shebangs too, but I'm not sure. |
Beta Was this translation helpful? Give feedback.
-
I did see the script, but it looks like it merely passes its findings on to other files. |
Beta Was this translation helpful? Give feedback.
-
oh, I only know a tiny bit about Ruby |
Beta Was this translation helpful? Give feedback.
-
No worries! Right now we only need to see how the detection is used. If it passes the shebang type as "'shell'", then it will respond accordingly. This is where we come in to find where the result(s) get processed. |
Beta Was this translation helpful? Give feedback.
-
I think it's here. (Sorry if it's kind of obvious) |
Beta Was this translation helpful? Give feedback.
-
Thanks for that! |
Beta Was this translation helpful? Give feedback.
-
However we go about this, it looks like one would have to modify |
Beta Was this translation helpful? Give feedback.
-
Huh. Maybe someone can add a |
Beta Was this translation helpful? Give feedback.
-
I would really like to know how does |
Beta Was this translation helpful? Give feedback.
-
It is a collection of files that define the coloring of words when they're uploaded to GitHub. Were you thinking of something of it that relates to this issue? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Agree with you |
Beta Was this translation helpful? Give feedback.
-
Although it is a great thing that the Shell language has been included in
languages.yml
, it can be difficult to find out what shell(s) a repository is meant for.After all, each different type has their own set of commands that they support.
There is a caveat or two with this enhancement request, though.
A lot of the files are not labeled by the extension, but rather by the shebang. So I am thinking that there will have to be a way to check what type it is (unless the interpreter already accomplishes that for us).
The other concern is simply letting users know the specific type while also conveying that it is still a shell script. Maybe different names, but with the same color? Maybe even
Shell - Bash
orShell - Zsh
instead ofShell
, and keep the same color that the Shell language already uses.Besides the suggestion above, it could be done easily if there is a way to make some kind of customized name with a
.gitattributes
file likelinguist-language
.Beta Was this translation helpful? Give feedback.
All reactions