planet 

Have you, like me, had to switch to an external debugger or run raw gdb in the terminal plugin to debug the C/C++ application you develop with Kate? That might not be necessary any more. There is now a “GDB Plugin” in trunk that gives you the power of raw GDB with some QAction candy for the most common actions. I have always been a bit frustrated with not having a debugger directly in Kate, but too lazy/busy to start a debugger plugin project. Read More

It’s me again. Given how much people seem to like the plugin, and that some would like to see this plugin replace the existing simple list view, I’ve put in a bit of work to make it so the tree view plugin replaces as much functionality of the original file list as possible. There’s now a list mode (which was surprisingly easy to do), as well as the tree mode and I’ve extended the sorting support to include all but the “custom sort order” option of the original file list (it’ll take a bit more work to support that, if its something people actually use, I just haven’t felt like doing the work to get drag and drop to work, and before now it didn’t make much sense to add). Read More

Kate has been my favorite editor for some time now. And only recently has it not been able to do something I asked it do to. I was working on a rather large project in Perl when things started getting confusing. The classic file list had 50+ files in it, some of them have the same file name, so would have (1) or (2) or even (4) after the file name, and while thats handy, it gets confusing pretty quickly. Read More

In recent KDE releases up to version 4.4 Kate unfortunately very often selected the wrong encoding. The result is that e.g. german umlauts (öäü) show up as cryptic signs in the text editor. What I’ve seen lots of times is that in this case people start to fix those characters manually for the entire document. In other words: They totally do not get at all that the text document simply was opened with the wrong encoding. Read More

Hello planet, As Google Summer of Code is now finished and I have successfully passed the final evaluation, I would like to give a brief description of my project. Kate is now able to recover (most of) what was written after last save in case of a crash or power failure. A swap file is created after the first editing action on a document that was successfully saved. If the user closes the document normally or saves its content, the swap file is deleted, otherwise, if Kate crashes, it remains on the disk. Read More

Each night now Kate (part/app) is build from git and all unit tests are run. Yeah, we even got some tests .P Until now, that just reminds on of our failures ;) But I hope the daily mail will perhaps motivate me and others more to fix them ;) Beside, thanks for all the people working to write these tests, like Bernhard, Dominik and Milian. Kate Nightmake Tests From: cullmann@kate-editor.org To: kwrite-devel@kde. Read More

While setting up the new server for the Kate homepage, I actually found again old stuff ;) Amazing that mails nearly ten years old can still be somewhere on the filesystem. Perhaps a little hint, to post the beginnings of what today is Kate/KatePart/KWrite and KTextEditor. Ten years ago, I asked the original author of KWrite, if he is interested in a MDI version of it (sorry, german, original mail): Read More

The website is now on a new server, which is a lot faster than the old one and software/hardware is fresh again. Hope the problems we had in the past few weeks are over now. No other real downtimes are planned, perhaps some reboots but nothing more than some minutes ;) Hope I can now finally setup my planned automated unit-tests and build ;) The DNS transfer seems to be faster than thought, still some people might arrive at the old server, where now only a stupid “Maintainance” page is up. Read More

In the last weeks, the homepage was sometimes down, as the server it is on is slowly dying. I just negotiate the transfer to a new one. That one will allow additional stuff to be run, guess we than even have nightly unit test runs (at least I hope so) ;) Therefor it may be, that the site is not reachable, as DNS transfer might always take some days.

Like told in previous posts here and there, KDE 4.6 won’t have a KatePart that supports the SmartInterface but instead KatePart moves on to the new and shiny (and much simpler) MovingInterface for the handling of automatic moving cursors and ranges. Now the big cut is done: KatePart in /trunk no longer implements the SmartInterface. KDevelop already adopted the new interface in a development branch, lets see how that all evolves. Read More