I haven't given up, but the bug is not yet fixed. I spent some time trying to find the cause without success. This bug apparently first appeared in TeXShop 4.66. Tools on the other half of the window still work. Thus it is not possible to switch from magnifying mode to text selection mode, and impossible to split the window. It is impossible to select any tools in the toolbar which are over the Preview half of the window. Szilágyi Zsolt reported a curious bug when using the magnifying glass in single window mode. The standard Font panel will open, allowing you to select a font and size. To modify these values, open the OgreKit Find Panel and then select the TeXShop menu /Source/Font/Show Fonts. In addition, the font and font size used in the Find and Replace fields of the panel can be changed and the changes will be remembered even if TeXShop is quit and restarted. This fixed a copy/paste bug in the ``Replace'' field of the panel. I know it's an early project, so I'm very optomistic about it.īTW, Would it be appropriate to have a TeXworks subforum here? I mean, if "WinShell" and "Scientific Author" get their own forums, surely TeXworks should make the cut.- Isao Sonobe updated OgreKit to version 2.1.12. I admit a tabbed interface would be nice, and master/sub-document settings, but these aren't big deals to me. As I mentioned, I prefer a dark theme (e.g., white or light gray text on a blue background) I think there's already an issue on google project page for support for this, which I've voted for, so hopefully it'll get done. But there is still no option for changing the primary editor and text colors. I looked at syntax-patterns.txt and it does look easy to alter. I'll try it on my laptop when I get home. I've just now installed, from source, the newest revision (r432) on my work computer, and it doesn't have those problems. However, this was the version used in the Application Bundles, which is quite early (r406), which I had been using on my laptop. 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 |