You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working with files that have no file extension to their filenames, such as unix shell scripts, is a huge PITA. To get syntax highlighting you either are forced to rename the files to add an extension (not always possible/acceptable), or else you must individually change the type selected from the default (text) to bash (in this case), for each and every file you're working with, and do it all over again the next time you open Brackets.
When dealing with a file with no file extension, or otherwise an unrecognised one (to cover extension-less filenames that do actually contain a dot), could brackets not look at the file's magic number (or the text of the file's first line of content) to see if it can determine the type and thus save me the time and frustration of manually doing so. It would be much appreciated. :)
The text was updated successfully, but these errors were encountered:
Issue by lrebrown
Wednesday Dec 03, 2014 at 14:02 GMT
Originally opened as adobe/brackets#10071
Working with files that have no file extension to their filenames, such as unix shell scripts, is a huge PITA. To get syntax highlighting you either are forced to rename the files to add an extension (not always possible/acceptable), or else you must individually change the type selected from the default (text) to bash (in this case), for each and every file you're working with, and do it all over again the next time you open Brackets.
When dealing with a file with no file extension, or otherwise an unrecognised one (to cover extension-less filenames that do actually contain a dot), could brackets not look at the file's magic number (or the text of the file's first line of content) to see if it can determine the type and thus save me the time and frustration of manually doing so. It would be much appreciated. :)
The text was updated successfully, but these errors were encountered: