From: Tim H. <tho...@te...> - 2013-01-07 22:48:01
|
Am 07.01.2013 22:50, schrieb Denis Bitouzé: > Le lundi 07/01/13 à 22h36, > Tim Hoffmann <tho...@te...> a écrit : > >> Ok, now I had a proper look and understand what you were trying to >> achieve. > I probably wasn't that clear. > >> This is one of the cases in which you can use the Config -> Custom >> Highlighting. Define your personal listings enviroment "foo" as >> verbatim there. Then the tex comment inside the environement is not >> parsed any more. > OK, nice. > > But, as said in another thread, the settings of Config -> Custom > Highlighting appear differently in texstudio.ini: > > 1. for a command, say \foo, it appears as a readable setting: > > customCommands=\\foo > > 2. for an environment, say 'bar', it appears as a non really readable > setting: > > customHighlighting=@Variant(\0\0\0\b\0\0\0\x1\0\0\0\x6\0\x62\0\x61\0r\0\0\0\x2\0\0\0\0) > > Is there a way to make customHighlighting as clear as customCommands? Well, you could. But the customHighlighting is more complex than customCommands. While the latter are just the commands themselves, the former are the commands plus the relation to the actual format (e.g. verbatim). And from the programming side it's easier to store this complete structure. In this case, don't worry what is written in the ini. TXS takes care to properly encode and decode it. Use the config dialog to modify it. |