![]() At times, nothing would be highlighted in an entire document for reasons I couldn't explain. Entire lines would be the wrong color if there was any command in them, and sometimes a color changed inappropriately in the middle of a word!. So it is not too hard to alter, especially if it is only the colours that you do not like.Īctually, my problems with syntax highlighting were more than just color preferance. Josephwright wrote:The syntax highlighting is stored in one of the config files (config/syntax-patterns.txt), and is done using regex's. The project as a whole goes in the right direction. But these are the only points on my wish list and they already have entries in the issues list. ![]() At the moment TeXworks manages documents split up into several parts with an additional special comment line right at the beginning of the included files. Two things that I miss are a kind of »Tabbed TeXing« and a minimal project management. I think that I will add this to the issues section of the project. Regarding Linux the documentation is not really clear in that point. ![]() The only issue is spell checking (no problem on Windows). The compilation process is described for several Linux distributions and in general is no big deal. Getting the code is very easy and I do an almost daily checkout of the SVN repository. A copy in the bin sub-folder of my home directory was enough. I managed successfully to compile it on my Linux system and I use the most recent version (r431). This has turned out to be much faster for me. I prefer writing commands by hand rather than clicking on the mouse and search them in menus or icon bars. In my opinion most other editors suffer from an overload of features which I don't really need. For me it is the project with the most potential for development. It has become the main editor on my both systems². ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |