However I feel like not everyone has invent account, so maybe it’s easier to juggle around some ideas here as well.
Here’s some of my personal wishes:
Make it clear the debug plugin can be used more than just GDB since it has DAP support (I will work on this at some point unless someone else is faster Basically need to do some renaming)
Streamline the session management (These are just my opinions on the matter, do tell me if I am wrong :V )
Sessions shouldn’t IMO handle plugin settings at all.
Plugin settings should be tied to the project the plugin is opened in, using .kateproject files.
Ideally, in my opinion, the flow is like this: Session holds multiple projects, projects hold plugin settings per project.
Some items like diagnostics etc. are a bit “all over the place” like build plugin has it’s own build diagnostics. I’m currently working on streamlining this since diagnostics panel has now nice filtering.
General streamlining of features (Please report more of these)
.kateproject files should be more upfront and there should be a tool to generate a kateproject template file, like VSCode has for some of it’s settings, like debugging tools.
Very big and difficult goal: Plugin creation without needing for C++ and building.
I know a couple of people who would be interested in making plugins for Kate but they really do not like writing C++.
Feel free to share your ideas here or the issue I linked above!
Kate Editor. There is one option I would like to see and that is ‘Column mode’. I have an old editor from another company that I use for working with text documents for my applications. Many times I have the need to create columns of miscellaneous information. How about a hot key such as ALT+C to turn column mode on or off? Great editor, Kate. I am playing with it now learning how to navigate it’s resources. Thank you.