Highlighting errors #281

Closed
svnpenn opened this Issue Oct 26, 2012 · 2 comments

Comments

Projects
None yet
2 participants

svnpenn commented Oct 26, 2012

http://github.com/svnpenn/dotfiles/blob/451c/.cygwin

This file is essentially a Bash script. I have noticed this about GitHub syntax
highlighting

  • If the file ends with a recognized extension, it will be highlighted
    correctly.
  • In the past if a file did not have a recognized extension, but was an
    "executable file" (file mode 100755) and had a proper Shebang line, then it
    would be properly highlighted.

Now the file is question does not have a recognized file type, but it is set as
an executable file and does have a proper Shebang line. Until recently the file
was highlighted correctly. Now it is still highlighted, but perhaps under the
wrong language. Comments are not being highlighted as such.

Simply stated I need to know how to get proper highlighting back for files with
unrecognized file extension.

svnpenn commented Dec 16, 2012

For "Shell" files you can get back proper highlighting with this hack. Just add the following line

## ## ## ## ## ## GitHub highlight hack
Contributor

tnm commented Dec 24, 2013

Closing, since we now treat shebang lines as authoritative.

tnm closed this Dec 24, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment