There is absolutely no need to create a second JSON syntax highlighting wordfile if just one more file extension needs to be recognized for syntax highlighting JSON files with a different file extension than JSON. It should be automatically syntax highlighted as JSON file indicated in status bar. Now open the nfig file using JSON format. uew into same directory as json.uew, i.e. Use Save As and save the file for example as json _appname.Replace File Extensions = JSON at end of first line of json.uew by File Names = nfig (case-insensitive interpreted name of the file without path).Using CONFIG as file extension was definitely no good idea by the developer of the application as it does not give any other application or a person an information about format of the file containing configuration data.Īnother method to highlight just nfig as JSON file by default and all other *.config files as XML files working only if the file name does not contain a space character is using a file name specific syntax highlighting. Restart UltraEdit if the indicated language in status bar is still XML. Now open the *.config file using JSON format. Remove from first line of xml.uew the file extension CONFIG.Append at end of first line of json.uew the file extension CONFIG (interpreted case-insensitive) or insert this file extension before JSON.Close the configuration dialog with button Cancel.Select language JSON if not already preselected because active file is syntax highlighted with that language. Open Advanced - Settings/ Configuration - Editor Display - Syntax Highlighting.ForceRs, I suppose you have edited the wrong json.uew by editing the file in wordfiles subdirectory in program files directory of UltraEdit or you have forgotten to remove file extension CONFIG from wordfile for XML files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |