Kate: Shortcomings of .kateconfig file

Sunday, 23 July 2006 | Dominik Haumann
Assume you have a .kateconfig file optimized for C++ code that replaces tabs on save. Now you open a Makefile that contains tabs (due to its strict syntax). If you save the Makefile in kate, the tabs then are replaced which results in a corrupted Makefile. In other words: The .kateconfig file applies to every file. It lacks mimetype/extension support and thus can lead to unwanted behaviours. So if you use a . Read More

Indentation and Coding Style

Sunday, 23 July 2006 | Dominik Haumann
kdelibs will have coding style conventions. In general. this is not a bad idea. Our 45528 slocs in KatePart all use a consistent indent-width of 2 spaces. Changing this does not really make sense – ok, if svn praise -w (sure, we never need svn blame in our code ;) finally works, we can discuss this again. In other words: How “consistent” will kdelibs get with this new conventions? The interesting part of Zack’s mail is Read More

Kate Project Plugin

Thursday, 20 July 2006 | Dominik Haumann
It is not a secret that removing Kate’s project manager in KDE 3.5 was not the right thing to do. It seems a lot of people used it and we got many complaints about this decision. That also shows that it is hard go get feedback about what users are really using. If a feature is done well, noone will ever talk about it. This is paradox, as we thought the project manager was not well integrated :) (I still think that) Read More

Triple clicks

Friday, 30 June 2006 | Dominik Haumann
Text editors and line edits support the so-called triple clicks according to [1]1. The document says Triple Click: Select the targeted row. […] It is unclear whether the “targeted row” includes the trailing linebreak. Kate Part selects the targeted line including the linebreak. You get the following behavior: If you move the selected row with the mouse, you usually have the linebreaks right. The same applies for copy/cut & paste. Read More

Kate Part in upcoming KDE 3.5.4

Wednesday, 28 June 2006 | Dominik Haumann
The last week was highly productive for Kate Part, as the following bugs were fixed: 89042 while pressing “del” key kate crashes (crash, bt) 103648 Codefolding Crash – Reproducable 118584 scroll position not upgrading (dynamic word wrap) 119435 kate crash when a file is saved 123315 kwrite/kate crashes randomly after save 124102 changing syntax highlighting when code is folded crashes katepart 127928 kate crashes deleting a block of text 128690 Dynamic word wrap makes text input slow 129853 Horizontal scrollbar and view not synced, if dynamic and static word wrap are off and some minor issues That are 6 crash fixes. Read More

Kate Modes & Filetypes

Thursday, 9 February 2006 | Christoph Cullmann
Modes allow the user to override the default configuration for documents of specified mimetypes or file extensions. When the editor loads a document and the mimetype or file extensions match for one of the defined filetypes, KatePart will read the configuration from the mode and apply the modelines defined. If more filetypes match, the one with the highest priority will be used. To create a filetype, go into the settings dialog available in Kate via Settings > Configure Kate > Open/Save > Modes/Filetypes, then press the New button and fill in the properties. Read More

.kateconfig Files

Thursday, 9 February 2006 | Christoph Cullmann
Kate allows you to specify local document variables by setting the corresponding modelines. The hidden file .kateconfig provides exactly the same functionality, but for all files in the directory. Enable the Feature To use a .kateconfig file you first have to enable the feature by invoking Settings > Configure Kate. In the config page Open/Save you can find the option Search depth for config file, which defaults to Do not use a config file. Read More

Kate Modelines

Thursday, 9 February 2006 | Christoph Cullmann
Kate Part’s modelines – also called Kate document variables – are Kate Part’s implementation of document variables, similar to Emacs and vim modelines. Document variables can be used to set Kate settings local to a file. This is for example for using another indenter than the one defined in the GUI settings. Or assume you work on two projects, the first indents with spaces and the second with tabs, then you can simply add a modeline that contains the specific document variables that set the specific indentation properties. Read More

Writing a Syntax Highlighting File

Thursday, 24 March 2005 | Christoph Cullmann
Note: Please refer to the Kate Handbook for the most recent version of how to write syntax highlighting files. Hint: If you want to write a syntax highlighting file, the XML Completion plugin might be of great help. This section is an overview of the Highlight Definition XML format in KDE4. Based on a small example it will describe the main components and their meaning and usage. The next section will go into detail with the highlight detection rules. Read More

Writing a Kate Plugin

Tuesday, 6 January 2004 | Christoph Cullmann
Introduction First at all, why writing plugins for an editor ? Good question, and I hope I have a good answer: Because we want Kate to be small and all extended features not all users need should go into plugins (like CVS suppport, project managment, coffee cooking ;) Therefore Kate provides a quite full-featured plugin interface and interfaces to all important stuff in the Kate application (the documents, views, windows, sidebar …). Read More