As many other applications Kate has the menu File > Recent Files, which lists all files you recently used. This recent file list right now is per session, i.e., each session has its own entries listed as recent files. Now there is a request to change it such that there is just one single global recent file list. I think having two recent files menus (one for the session and one global) is a bad solution. Further, adding an option for that also sounds wrong.
To change or not to change, that’s the question?! :) What do you think?
Hi! It’s me again. Got some exciting news.
The file tree is now the default (and only) document list/view widget. It actually took me by surprise. After I got the list mode and other features implemented, the old document list was unceremoniously ripped out, and extensions were added to allow kate to always load a given plugin, and give its settings tab a little more prominence.
Since then however I’ve fixed a few issues regarding the settings in the plugin. The file tree settings tab now sets the plugins global settings, and will clear out the setting overrides for the current session so they will get pulled from the global settings. And I just finished up adding back the “Go” menu, and the “next” and “prev” document shortcuts.
Just to be clear, you are NOT forced to use a tree view from now on. That is just the current default. You can switch to list mode using either the settings dialog (which will apply to kate globally, minus any sessions you have used the document view context menu to change the mode for), or using the context menu on the document view (file tree) widget.
Thank you to everyone who has used my plugin in the past, and to everyone who will be using it in the future :)
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. Fortunately Ian Wakeling started this GDB plugin and got it off the ground. When I got introduced to it at Akademy, it triggered an itch in me to get this plugin into kdesdk and to add some features for the more point and click type of persons. As it seemed I had a bit more free time to spend on the plugin, Ian let me take over as maintainer.
Main features of the plugin:
– Jump to the corresponding file and line whenever gdb stops.
– Insert and remove breakpoints.
– Tool-bar buttons for the most often used actions like step into/over/out. Those actions can of course also be assigned to keyboard shortcuts.
– Execution markers and breakpoint markers on the icon border.
– A call stack tab for point and click navigation of the call stack.
– Optional IO redirection to a separate tab.
– Printing the value of the currently selected variable or expression. QStrings and friends are not supported (yet?).
– And last but not least. A GDB console for the full power of GDB.