In the Scripts menu I see: * Emmet * Navigation * Quick Coding * Editing What is Emmet? Is that someone's name? The name of the category should be descriptive of what scripts it holds. Navigation has only two scripts, to move the cursor to the previous/next matching indent. Quick Coding has only one script, "Expand abbreviation", and a script by the same name is also in "Emmet". It would improve the user experience if you merged Emmet, Quick Coding and Editing into one category, or better yet got rid of the categories altogether as there are not enough scripts to warrant having them.
Emmet is a web-developer's toolkit, see https://docs.emmet.io/ The categorization comes from the "category": entries in the json data of https://cgit.kde.org/ktexteditor.git/tree/src/script/data/commands Unfortunately, these scripts are embedded into the binary, so I could not quickly test if removing the category works and places entries into the Scripts menu without a submenu, but maybe someone can propose a better naming/categorization.
DrSlony, can you please confirm Christoph's explanation above explains the plugins sufficiently?
Hey Since Emmet is an external plugin, it could be argued for Emmet scripts to remain separate. The "category:" entries link is dead. I see two entries in Navigation, one entry in Quick Coding and seven in Editing. I'm a developer and don't know the difference between Editing and Quick Coding. No point having a subcategory for two, let alone one, items. I would get rid of those rather empty and ambiguous categories and just have the entries right under Scripts. Furthermore, the Tools menu has entries such as Uppercase, Lowercase, Capitalize... These are effectively no different than the entries in Scripts > Editing, such as Sort Selected Text, Move Lines Up, etc. From a user's perspective, they all belong together. I shouldn't need to hunt through menus and submenus looking for something which has been (to me arbitrarily) categorized based on whether it comes from a script or not, or maybe whether it comes from a bash script or a python script or C++. What I'm essentially saying is that, unless it's common practice for KWrite users to modify what appears under the Scripts menu, it would be good to get rid of this sub-categorization based on where a bit of code comes from, and just list actions in one place, making them easier for users to find.
Sounds like a good plan.
Created attachment 140895 [details] Screenshot of Potential fix for Bug #396623
I feel like this is a bit much, but it is easier to find scripts than having to search through multiple subcategories
I think it would be much more helpful if the "Scripts" option itself was changed to something like "Navigation" or "Editing". Though, it is much more logical to provide a separate (automatically) toggleable toolbar action for Emmett since it is entirely dependent on the file the user is currently editing (HTML, CSS).
I don't think just moving this into one level is useful, then you have all Emmet stuff that is not always useful mixed up with others. We provide a hud now with ctrl-alt-i that let's you explore all actions list like. I don't see an urgent need to alter that menu layout.