Common 

Since KDE 3.5.4 Kate Part supports “smart end“. Right now it behaves like this when pressing “end”:

1. go to last non-space character
2. go to the last character (i.e. hit end twice)

I’m writing this blog to get feedback about what’s the right/expected behaviour. Is it as described above, or should we first go to the very last character, and to the last non-space only when hitting then end-key twice?

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.

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

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. Kate Part in KDE 3.5.4 will be more stable than ever :) That’s especially cool for KDevelop, Quanta+, Kile – well and Kate.
Special thanks to Andreas Kling for initiating the bug squashing sessions! You are like a blackbox: The input is a bug and your output is the fix ;)

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. To remove an existing filetype, select it from the dropdown list and press the Delete button. To edit an existing mode, select it from the dropdown list.