192 thoughts on “Kate: What’s cool, and what should be improved?

    • Powerful formatting capabilities.
    • XML formatting and folding should take into account the short version of tags (i.e. treat as a complete tag, not a first part of unclosed tag).
    • Like: Pretty much everything.
    • Improve: True multiline editing (multicursor), so I can ditch Sublime.
    • Like: easy to use editor with lot’s of ‘little things’ that make working with it more pleasant than other editors.
    • Improve: activity integration with KDE, opening documents from kio exec/file browsers etc. tends to jump to a different Kate instance in some other activity (instead of the one running in the current activity or starting a new instance…)
    • like: comes with KDE, same editing component as KDevelop
    • improve: Open files with line numbers like include/myheader.hh:203 should open the file and place the cursor in line 203.
    • improve 2: show matching bracets for <> especially for C++.
    • like: whats not too like?
    • improve: yeah, it is slow to open and stuff on windows (grasping at straws here!). Oh yeah! The line numbers changing in the periperal vision/status bar is distracting, maybe do them as fading in and out popup under the text cursor?
    1. About that Lua comment: please fill the bugreport, or visit IRC, it’s easy to fix the highlight file yourself with few hints.

    • Like: Stability and reliability. I’m using kate for 3 years, and I haven’t experienced any crash!
    • Improve: Ad-hoc highlighting support and overall improvement of highlighting engine, there is stuff you can not do with existing one.
    1. Change this in the settings; the keys are for “I want it changed for this view only”. The checkboxes in the settings are permanent.

    • Like: simplicity and ease of use
    • Improve: long lines (for example generated code) get split into multiple lines and this breaks files upon saving. This is totally unacceptable and other editors do not do it.
      1. No, that’s not the problem.
        For really long lines, kate force-wraps them.
        As above, I had to use a different editor to work with these files.
        Yes, the lines were really long, not sure whether the limit was 1000 or 4k, something like that.

        1. Yeah, that is rather annoying. Weird thing is it seems to support longer lines, because when you manually correct it, it works fine. At least that is what I have experienced.

    • Like: inner window tiling, the project plugin, minimap scrolling, fast, integrated with KDE, a lot of configuration options
    • Improve: autocompletion, command feature (like sublime), code navigation, easier to develop plugins (pate integration is halhway there), plugin repository
    • Like: VI input mode
    • Improve: Lines larger than 4096 chars. Even if you cant edit THOSE lines, allow editing the rest of the doc.
  1. Small, fast and clever.
    There are a lot of Syntax highlight definitions, but some of them is missing such as

    • rsync exclude file
    • .gitignore
    • gitolite config

    This would not be problem but the documentation of how to write syntax definition files incomprehensible without clear examples.
    Someone who knows nothing about the structure of the syntax definition xml can not write a simple one (see above) based on this documentation.
    So very very pain full to learn the syntax highlight definition.

    The .kateconfig file is useless, because it is applied to all of the files in the directory. What if there are two or more different kind of file in the same directory?
    Lack of http://editorconfig.org/ support.

    Undocumented “Project” feature. Partially implemented UI.

    The “F1” key and the “Help” button is context insensitive. It is always leads to the home page of the documentation. (Which is outdated)

    The UI of the “Font & color schemas” editor is a UX fail.
    Unclear property inheritance. There is no preview at all. There is no customizable text (source code) to preview per language.

    Very few documentation for snippets especially for scripts in the snippet package.

    With this problems (and several more) the KATE is the one of the best editor.
    Thank you

    • Like: Nice best-of-both-worlds spot between KWrite and KDevelop.
    • Improve: Code navigation. Pretty much the only feature I miss from Geany.
    1. Yeah. I’d love to see a code tree that will allow me to navigate across a large project (multi-file, multi-directory). It would make life so much easier.

      I spend half my time trying to figure out where the function is on which page.

    • like: Network transparency, speed, bookmarks and the search/replace features.
    • Improve: clean indention / Autoindent for php code, clean settings dialog, explain difference between plugins and extensions.
    • LIKE: vim input mode, minimap… all ?!
    • IMPROVE: ease the jump to “favorite” files (1)
    • IMPROVE: twig integration

    Yeah, two “improve” items sorry :)
    (1) I often have a lot of files open. I’d like to be able to “pin” some files (sort of “favorite” for my current editing session) so that I can very quickly switch to theses files. I know about the quick open dialog (ctrl-alt-o) and the color code in the filelist side panel but it’s not exactly the same need. Maybe these pinned files could have their own “favorite filelist” side panel, or a tabbar.

    • Like: Almost Everything
    • Improve: Multi-cursor support, Scrollable minimap (like Sublime Text), when file is really big the minimap is useless.
    • Like: Vi-mode & libkteyteditor
    • Imrove: relative numbering in vi-mode ; support of Vim plugins ; remaps of keys in Vi-mode
    1. Oliver, relative numbering was recently added.
      Vim plugins – we are little bit far from that
      remaping the keys – you can create mappings of your own, the problem is with the original mappins that can’t be remapped I think right now (but we are slowly getting there)

    • Like: simplicity, plugins, context-aware highlighter
    • Improve: Can’t think of much. Some plugins could use more love.
    • Like : syntax coloration, speed, saved sessions, terminal / XML validator integration
    • Would love : ability to group files from a saved session into the docs list on the left into “logical” groups, i.e. when you have say 20 files open, the ability to create groups with a header and drag and drop files into different buckets would help to visually identify what files pertain to.
    • I love the support for practically any script or source code.
    • I would like GetHotNewStuff integration for sharing and downloading color profiles.
    • Like: Sessions
    • Improve: “Projects”. What is that? Why can’t I use it? Why everything related to it is useless?
      Right now on my interface. There is a “Current Project” in my status bar that does nothing. “Projects” in sidebar also does nothing. And in the menu “Projects” there is only “Right” and “Left” which also does nothing.
    • Improve2: The interface could use some clean up. e.g. A side bar tab with only one entry, big status bar with little information, big side bar with only one document…
      1. Some functionality that can’t be used trough the user interface and requires the manual creation of json files to work, shouldn’t be enabled by default.

    • Like: fast, easy open many files to quickly look at new projects from command line.
    • Improve: When searching for a string I often end up looking for the same string in many documents. I cannot just press F3/ctrl-f to search for it again after changing the document, instead I have to enter/paste the search string again.
    • When text is selected, all the same occurence should be highlighted too
    • on the right bar, it should be more easy /more clear to open/close html tag (or hide/display tag’s content). The user experience need to be better to help him to know in wich code part he is. (Check Notepad++)
    • Like: Ease of use.
    • Improve: Alert when file content changes on disc. Change colour, show an asterisk; anything but a modal dialog I have to dismiss to carry on with working on other files.
    • I like the MDI (and just about everything else, because Kate is great)
    • Startup time decreases and a built-in word count option would be nice
    • Like: simple to manage lots of files
    • Improve: please get rid of the character-limit per line
    • (Wish: something like ctrl+tab for switching between documents as implemented in browsers between tabs)
    • changing 1 character in minified files is either impossible right now or nearly kills kate (performance wise).
    1. – pros: Kate is very nice and already has most of the features requested above (for instance, one can switch off line wrapping).
      – cons: It could be easier to use with projects and git (especially without writing your own .project file).

    • Like: Sessions – just sooo good
    • Would like: more/better documentation on scripting, more flexible code folding
  2. Cynic: Please make a file called “.kateproject” and only that, no name before the . in the top level directory of your project. It will be a hidden file in Unix.
    Here are the contents of one of ours (hopefully it won’t crap out in the blog)

    	"name": "Awk",
    	"files": [
    	{  "directory": ".",
    		"filters": ["*.c", "*.h", "*.y", "makefile", "awk.1", "README", "FIXES"],
    		"recursive": 0
    	"build": { "directory": ".",
    		"build": "make",
    		"clean": "make clean",
    		"install": "make install"
  3. Like: EVERYTHING. Seriously there’s just far too much good stuff.

    Improve: I’d like to see use of a scanner so kate stores and handles tokens, and we don’t have the same routines being run over and over, eg there was a change not so long ago that added lexing for C++ i think, and all the info was just thrown away after use. This would also make highlighters and indent scripts run a lot faster, and more accurately for syntax.

    Apart from that, I’d like to see a period of consolidation: the projects plugin showed how good integration can be, and I think there’s a lot of scripting possibilities from that. So in line with the recent improvements to Build Plugin, I’d like to see kate really get polished for KF5 (since my other suggestion is never going to happen in time;)

    (wrt above, just use standard double quote, and it’ll be fine, cynic. you may have to quit the session and restart kate if you make changes; the refresh button doesn’t seem to work in my distro version. i’m upgrading now..)

    • Like: tabs, terminal sync.
    • Improve: button to start/stop terminal sync, document ordering should change when reordering tabs, meld functionality for comparing files.
  4. • Like: Highlighting of identical names when clicking a variable
    • Improve: Files in Document-View should have a more verbose context menu (when right-clicking with the mouse) containing at least “rename” and “open file manager in directory containing this file”

    • like: Block selection, fast start, autocompletion, (probably many many more things that make Kate my favorite graphical editor, …)

    improve: 2 things come to mind:

    • limitations with long lines (I usually raise the limit, but still… Kate becomes a bit slow when there are many loooong lines (i.e. > 8k chars/line) – I move to vim in case I have to modify such files – usually you only want to change a few characters in such files)
    • Regular expression: I’d like to have PCRE. Also, when searching with regexp enabled, Kate does not search/mark the text while typing. This could be enabled (in case the RE is valid)
  5. is kate-part also ok (Kwrite user here)?

    • LIKE: scrollbar mini-map, KDE integration (especially with color schemes), lots of options, powerfull, but small editor.
    • IMPROVE: Configure toolbars, one toolbar apparently consists of two? and it is not possible to move icons around like one would. I think this needs be completly rethink.
    • IMPROVE: as Heiko Tietze suggested, I don’t understand the reasoning behind having options twice (in the menubar and in the settings dialog). This is quite unusual and thus unexpected. Please get rid of it.
    • Like: quick to start, support for every syntax I’ve ever needed, clean interface.
    • Improve: easily changing settings per session, for all the documents in that session but only for that session.
    • Like: User interface.
    • Improve: The code folding is a little to easy to accidentally click, especially if I am trying to select a block of text.
    • KIO integration is the best advantage over other editors.
    • There’s a few “half-baked” features (like the project plugin) that are extremely difficult to use. Give them some attention and love, or drop them altogether rather than leaving things in an awkward, non-user-friendly state.
  6. Loving Everything.
    Wishing the Projects Plugin would expose functionality to ease repository tasks, eg:

    Add file to current project when saving.
    Revert a file to a previous point
    Revert a project
    Get Status of Files vs upstream
    Diff file vs another version
    Add Tags/comments
    Commit / Push / Check-in
    Check-out, Switch Branch

    Of course I mentioned Git in the above but these should probably be VC system agnostic.

  7. I’d like smarter defaults for the location of new files – currently they go to my Documents directory instead of the sub-directory of the project I’m working on… Or generally, some intelligent defaults for detecting and handling “projects” and guessing which open files belong together based on a common root path.

    I like Kate because it has the right amount of balance as a fast and light-weight option between a (too) simple text editor and a massive full-blown IDE.

    • Like: reg exp engine in search/replace :-)
    • Improvement: i) word/character counter so that I do not need to paste the text into LibreOffice just for that simple operation
  8. Like: Powerful formatting options.

    Improve: Paste text at the text-cursor position rather than the mouse cursor position.

  9. Like everything about it! The auto completion support would be complemented by using clang; the existing auto completers are very slow. I do use KDevelop most of the time, but kate is nide for those little edits

  10. Like: everything
    Just 2 wish: please add cursor history I.e jump back and forth between previous cursor positions and do not remove multi window

  11. Like: VI mode, Pate plugin, overall modularity

    o VI mode (split window and navigate between them)
    o Pate plugin (python API) , plugins repository

    o Command Palette to quickly access Kate functionality (Sublime Text, Emacs M-x)
    o Terminal buffer (like emacs ansi-term)
    o Webkit browser plugin to preview markdown document or browse documentation on the web

  12. Like: All the little shortcuts that make life easier, eg shft+alt+down
    Improve: Html highlighting with php and foldable html tags
    Request: ability to save all open files, eg of a session/project, into a folder with their original directory structure, eg save_folder/a/one.php and save_folder/b/two.php

  13. * Very nice, simple and powerful
    * Add Ctrl+click to open css file in tag on HTML code
    * Improve tab manager: add a menu when multiple files are open (like the last release of KDevelop)

  14. I need to use SciTE instead of Kate for only one purpose: to open up files that have their line feeds stripped out and are one long line. This happens a lot in web development when .css or .js files are “minimized” to save precious bytes.

    Kate can open them, but complains. Kate is also VERY SLOW at scrolling such a file when “word wrap” is turned on. Agonizingly slow. And thus I need to use Gedit or SciTE.

    Is there any way that Kate can have arbitrarily long lines?

  15. – like: internal terminal, split views, search in folder
    – improve: Multi-line edit like in VIM and Sublime, more and better color schemas

  16. + light, fast
    – can’t edit very long lines
    – slow with large files
    – search & replace ui is absolutely horrible

  17. Cool: The syntax-highlighting :)
    To be improved: It should remember spell-checking, line-break etc. settings, per session (not just kate, also all the programs using KatePart – it’s seriously annoying to have to set up all of this again each time I start Kile)

  18. Like: navigating in folder tree structure
    Improve: drag and drop function like in Quanta (all files should be dropped into html as relative links, except images that are dropped like img tags)

  19. Like: Mini-map scrolling

    Improve: Bracket block minimizing (the highlighting will work great, but it’ll roll up the whole rest of the document or at least a lot of extra stuff)

  20. Like: the new column edit – been asking for and wanting it for years
    Improve: smart brackets 1) mark some text, press opening bracket/parenthesis/quotes, have automatic closing of same character. 2) do NOT overwrite closing bracket/parenthesis/quotes when typing one next to it.

  21. like:
    the over all usability

    a biblatex syntax highlighting
    the multiple file management is a bit awkward

  22. like: lots: multi-document, multi-window
    improve: meld functionality for comparing views (not just on saved files, but also unsaved documents)

  23. Love: the documents tree.

    Wish: I wish the plugin API was both more powerful and better documented. The other day I wanted to write a plugin that lets me click (or ctrl-click or something) on code and have it send me to the docs for that function. It seems like the plugin support is almost only for what has already been thought of, or for new widgets.

  24. What’s cool : Kate + VI mode = the best of both worlds.
    What’s should be improved : better default color schemes.

    Thank for your great work ! I use Kate everyday and it’s a such a powerfull editor. There is too much low-quality/useless applications shipped with KDE vanilla, but Kate is really a killer app.

  25. If i could have a second chance, I would say
    What should be improved: better automatic code folding (now the only option is to fold top level nodes, no way to fold everything) and option to save all opened files to a folder but into subfolders keeping the structure of the directories they originally lay into.

  26. like: very good support for regexps. Before kate I have used perl onliners for search replace a lot. With kate is is much more convenient to do it.

    impovements: please have very close look to textmate on Mac. This is the only comparable editor to kate. So it would not hurt to get some inspiration and copy some little small improvements which kate is still missing. To get some idea, look at https://www.youtube.com/watch?v=jmhp1-nHd9c but certaily there is more.

  27. 1. it is really multi-functional and universal tool
    2. ability open files which paths given (written) in opened document (for example the “include” files or other text files)


    * It’s really fast, yet has most of the features I want from an advanced text editor such as split view, good syntax highlighting, block selection, search in files, session management, and “highlight selection” extension. In fact, Kate & Dolphin were the major reason why I moved from GNOME to KDE, after seeing how fast & featured Kate & Dolphin were, even on GNOME!


    * Allow to go back & forward in view history. eg: You press PageDown a few times then switch to a different tab. Hitting “Back” should go back to that place in the original tab and then “Back” several times again should take you back to the original location. Currently, Alt+Left/Right goes through your recent tab history but not your recent location history.

    * The “Search in Files” feature is extremely useful (particularly for programmers), but it is a hassle to open & close the panel. It should be easy to open it (eg: with a shortcut) and close it (eg: with a shortcut and with a Close button). Currently you have to click on “Edit -> Search in Files” to open it, and “View -> Tool Views -> Show Search and Replace” to close it, so this is hard to find and becomes annoying if you want to do it often. Also, it would be great if the “Search in Files” results was shown either as a single list or if the current tree view had all items open, so you can easily just scroll down to see all results in all files at once, instead of clicking to view results from one file at a time.

    * Allow manually shuffling around the tabs, such as if you want a few tabs to always be at the start of the list or grouped together compared to other tabs. I currently have to close all files and re-open them in a certain order to get this! (I’m using “Multiline Tab Bar”). Even adding “Move tab higher / lower” to the context menu of the tab-bar would allow this.

  29. Like:

    So much… but one of my favorite features is that remote file handling works same as local. No separate widgets for FTP, SFTP, etc… one unified whole. Why does no other editor have that?


    Only that my favorite KDE feature ever has disappeared once again. Used to be that with automatic brace/parens/quote matching (not the extension but the built-in feature that is now gone) you could do all sorts of cool things such as highlight a string, hit the left parens ‘(‘ and automatically the text would be wrapped with a right parens. It also worked for braces, brackets, single and double quotes. Quite simply the best timesaver I have seen in a text editor, and now… GONE.

  30. My favorite feature of Kate is its syntax highlighting. It has the most beautiful syntax highlighting I have ever used in any text editor. Kate is also feature-rich, with several useful plugins, and it is under constant development. These are some of my favorite features of this remarkable text editor.

    As for shortcomings, the following are what I can think of. Although Kate supports many programming languages, some are absent, a prominent example being the lack of Squirrel support. Another shortcoming is its lack of documentation concerning some of its plugins, which prevents me from understanding how to use them.

    I have some other gripes with Kate, but that is largely because I tend to view Kate as a replacement to other Integrated Development Environments, and, as such, I suppose it is not proper to list them as shortcomings. Moreover, Kate is already becoming better and better with each version, and I would like to thank the hard-working developers who labor on each new release.

    Overall, Kate, as I have said, is remarkable. Therefore, it is right now the principal tool I use for my development projects. I look forward to the new features Kate has to offer to make a developer’s life even easier.

    Thanks for your effort! I appreciate it. :)

  31. I really like to see reStructuredText text highlighting for code blocks:

    .. code:: python

    print(“A literal block directive explicitly marked as python code”)

    Thanx! :) (BTW vim support it!)

  32. Like: Customizable highlighting, uncluttered design.

    Dislike: Alt-Left and Alt-Right going by position in the document list (useless) and not by opened document history for the specific window (very useful). Ordered by “last time document changed in this window”.

  33. A few people have mentioned wanting a syntax higlighting file, or a “missing language”.
    If you want it added, /join #kate on IRC: chat.freenode.net and I for one will help you write the highlighter file; 9 times out of 10 they’re very easy, but it does require someone who uses the language to drive the effort, and add new keywords etc over time.

    There’s a couple of others in there who regularly work on higlighters too; everyone in the channel is very supportive, so get involved. :-)

    1. Thanx for good idea! :) But ReST and markdown are a little more complicated than just add new keywords. It could be probably good idea to make python plugin for it ..

  34. I love working with Kate, but https://bugs.kde.org/show_bug.cgi?id=83301 should finally be addressed – it’s been open for over 10 years now, and it’s probably no biggie to implement. Writing LaTeX or other text documents with lines as wide as your screen doesn’t exactly make text more readable. It should be possible to have lines break dynamically at e.g. the position for hard line breaks.

    Another thing that should be addressed is making it possible for regular expressions to be non-greedy, e.g. \w+? is an errorneous expression according to Kate.

  35. *) LIKE : its lighweight :D
    *) IMPROVE : i wish there’s plugin that enable to chat with friends (gtalk,jabber,facebook, etc.)

    sorry for my bad english :)

  36. * Like: Split view, the documents sidebar, and Ctrl-D to comment code
    * Improve: folder display in documents sidebar. If I’m editing files in A/src/ and B/src/, it’s not helpful to see two top-level folders called src/, because I can’t tell which is which (frequently, I have ~10 folders named “src/” listed in the sidebar at once). Include the A and B to make the pathnames unique.

    1. as a workaround you could (create and) open file at A and B folders. (for example create todo or readme)

      I like to have shortcut to find file name in doc sidebar (I have open pretty much of them)

  37. * Like: Easy to learn but powerful
    * Improve: Restoration of External Tools plugin
    * Improve: Richer JavaScript API. For example, a function like system() in VIM, which gets the output of the shell command, in place of External Tools plugin.

  38. ♥ Like: Everything :)

    ✔ Should be improved: File System Browser plugin that currently slows down the start up of kate; when I disable this plugin it starts as it should (fast).

  39. LIKE: syntax highlighting is fantastic. i use a lot of custom words and colours–makes it very easy to understand code at a glance. the folder/file display is something one can not give up after using.

    DISLIKE: code folding was great, then revised and ruined for me. can not fold at a specific level now–it boggles my mind that programmer would think it’s OK to just drop a feature like that. terrible for coding classes and almost a deal-breaker. at the very least, if it remembered “manual” folds in the session, but that seem not to work either.

  40. LIKE: All the animated gizmos that help to find matching elements in the code. Code map (especially with code change indicators). Overall looks and feel of the editing area.

    DISLIKE: simplified code folding options – I really enjoyed working with Kate, and after code folding ‘update’ I’m not using it at all (reverted to Wine/Notepad++ instead).

    IMPROVE: persistent folding states. Folding state data could be stored locally, and contain file path and a file checksum – if both matches the actual file (tested on opening the file), folding states should be restored. It could work independently from sessions. I suppose sessions already should allow that, but it never worked for me. Maybe I didn’t try hard enough, maybe it simply doesn’t work for remote files, or it doesn’t work at all.

    SUGGESTION: Add a syntax highlighting scheme that mimics old black and green (or black/amber) displays. Red/bright colors for highlights and errors, shades of green (maybe some other non-conflicting colors) for normal code. That would be really cool.

  41. Like: Spellcheck, brackets highlighting.

    Want: A “Brackets check” function that parses the whole document (for text docs rather than programs) and highlights ALL bracket-pair contents. This would help locate missing closing brackets – a common error in my text documents!.

  42. Cool: Reliable; super fast and easy to customize; clean, easy on the eyes IDE; logical menus; features available but not in your face; tools, highlighting, code folding, sessions, command line — Kate can be customized for how you work best, not how someone else thinks you should work.
    Improved: API documentation and broken features; documentation is getting harder to find; most online links are broken.

  43. Drop the tabs. Drop double-click to switch document in the “Documents” list. Make it not take 4 seconds to open/close a document. Kate used to be my favourite editor, it still is, but it hurts me that it is so slow and becoming more clumsy to use.

  44. LIKE: code map, code completation, customizable *
    DISLIKE: map still shows whole code when there is 1500+ lines, it becomes impossible to get where I want via map

  45. Like: Everything – awesome all round editor
    Improve / feature request: Highlighting for repeat text in the scroll bar (like chrome does). This will allow you to see all the repeat occurrences of the highlighted text in a single glance. The Minimap is pretty cool, but it’s too bulky!!

  46. Like: Snippets.
    Improve: Don’t bury them in a hierarchy of menus! (I miss the paste applet really, but quick access to snippets would be almost as good.)

  47. When I have multiple instances of Kate open I’d like to be able to drag and drop tabs between the two instances.

  48. Another item: We should be able to set a default “open” folder in preferences. As it is, its stuck on “> Home > Documents” and there is no way to change it. It should be customizable in preferences (This has bugged me forever)

    1. Sadly, despite removing important level-based folding options (they are commented-out in code, and completely removed from menubar source), Kate still has annoying bugs, like folding code at random nodes in a way that makes it impossible to fold anything below that point (you need to manually find and unfold offending node to get that fixed).

      Another one I just came across (and another show stopper for me) makes code map useless. I’m talking about those color dots indicating code changes on document map. Brilliant idea for quick code scrolling, but when code is folded, they are shown in wrong places.

      It feels almost like someone is sabotaging this project.

      Anyway, NP++ works fine under Wine, you only need to remove titlebar from tooltip windows, so the autocomplete and function hints won’t obscure your code as you write.

    2. well, i am finally giving up on this editor. the code-folding mess has become unbearable with recent, complex projects. a shame really, because it was all great several years ago before somebody thought they would “improve” things.

      1. Well, probably the comments on code are written in more inclusive language now. You have to be happy about it, or else…

  49. Like: split views, column edit
    Need: better code folding and customization: add code folding for multiline comments, make easy for user to add keywords to existing keyword group, add new keyword group, create-your-own language template for highlighting, code folding, comment styles, etc.

  50. like: mostly everything, my editor of choice for a long time
    need/improve: multi-line tab bar extension in plasma 5 is missing ?

  51. Like: Automatic highlighting of the same word in a document.
    Improvement: The option to strip out trailing whitespace in unsaved documents was removed. My workflow depends on a lot of copy and paste from the terminal to internal ticket notes. Trailing whitespace has been known to creep in, especially when using Konsole. There is no reason to save the document locally at all, so relying on stripping it out when saving the document adds an otherwise-unneeded step to my workflow. Please see about adding this feature back in.

  52. The applied word wrap cannot be unwrapped. Static wrap is selected
    in the Configuration.

    Kate Version 3.13.3
    KDE Development Platform 4.13.3
    Xubuntu 14.04 32bit

  53. really big files are impossible (e.g. mysql dumps where I need to change the first “use …” line only) – could it not load limited amounts of text to memory then load more on-demand if we scroll?

    1. Late in the game…
      That´s a really good idea. Don’t know how difficult it would be to implement though.
      Good old TECo editor worked this way, reading the file by pieces.

    1. you can (if you rly do not like the highlighting) just switch off highlighting for tex in the config. Should this fail you can still find and remove the syntax file for tex.
      Or if you just think the current highlighting isn’t precise enough find the tex highlight file online and add it to kate and tell kate to use this one for your tex files.

  54. i like the “build” ide and need for that EXTRA the feature “save with autonumber-BUTTON” beside the normal save-buttons, the new (3rd) save-button will automaticly save the file with the preset name and with the NEXT “build-number” ,…, PLEAZE !!

  55. The folding should be improved.
    In particular there should be an option to unfold all, that now is missing.
    This is very relevant, because often kate tries to fold improperly chunks of code that are partially folded, failing in folding properly.
    An unfold all option would help to avoid this problem.

    1. I doubt it will be fixed anytime soon (if ever). But in your case CTRL+a, CTRL+x, CTRL+v sequence should leave your code in completely unfolded state. Beware though, bigger files (30K lines or so) can take some time to paste.

  56. I really love Kate

    Cool: search strings in folders (practically greping in the editor)

    Improvable: bookmark color auto-bleaching . why? Please just let me pick the actual color!

  57. Better identified completion. Use not only context of the current file but of all open files. Also use keywords of the current language

  58. Generally an awesome lightweight editor, likes:
    – project view
    – syntax highlighting
    – auto match highlighting
    – regex replace

    Please add/improve:
    – Work properly under Linux Mint (GUI all borken / no buttons)
    – Regex FIND not just regex find/replace
    – Show hidden/control chars (EG newline, tab)
    – Ability to add a button that puts it straight into (for example) ‘C’ mode rather than having to traverse submenus

  59. – Love the ability to use regular expressions
    – Would love the ability to copy only those lines in a file that have been found using a regular expression

    1. When I work on a remote file (ssh) and click on “open file” kate tries to open a dir with the full path including the file name of the already open file and then shows an error message that the dir doesn’t exist. Other than that I love Kate.

  60. Nice:
    – Kate has a good UI, especially about searching / replacing texts, and finding files.

    – Support persistent undo and undo branch like vim
    – Better project support. When user selects a file which belongs in a Kate project on window system, Kate searches a owner instance which currently opens the project, then gets the instance opens the file.
    – Improve grep performance
    – Improve windows installer. support to associate file types in installation.

    1. One more request:
      – Add a plugin to support GNU GLOBAL.
      GNU GLOBAL now can supports many software development languages using lexers of Pygments to create tags of source codes.

  61. I like how Kate v15.12.3 can open a 500 MB text file in three seconds.
    But Kate v16.08 takes 50 seconds so I want Kate’s performance restored.

  62. Version 15.12.3

    The search bar hides the status bar so when I search a text I don’t see the actual line number.

    It would be great to have an option to disable the search as you type feature. In most of my cases just a waste of resources and annoying that the selection jumps especially as I cannot see the line number because of the issue mentioned earlier.

  63. Tabbar is most annoying thing for me, it starts to hide tabs when it shows 5-6 tabs!!! Please do not hide tabs, but squeeze them! it is so counterproductive to press +1 and then look for your tab! There was nice Tabify plugin why did you remove it?

  64. The Search and Replace plugin (Kate v 17.12.3 – in Kubuntu 18.04) would be awesome – if it didn’t completely freeze the system for several minutes every time I try to use it. When I start typing the string to search for, it freezes. It appears related to ‘search while you type’ but I can’t be certain. Bottom line is that it’s unusable, and it breaks KDE itself – as Kate isn’t just frozen, everything else is also frozen, and there is no way to kill Kate when this happens as nothing else works.

  65. While I do use Kate for some scripting/coding, I also use it for just making notes for myself. I’d request the ability to bold, italic, underline selected text.

    1. In Reply to Kronykus

      OK, it’s time for a lesson:

      – Word processors produce fancy printed output, with formatting

      – Text editors manipulate text on disk, without formatting

      Next week’s lesson: Syntax Highlighting

  66. I am running Kate both on my Fedora 28 and Windows 10 LTSB. I was looking for a long time for a text editor on my windows with extended functionality. I always install Kate on my linux installs and was surprised to see a windows build. Naturally needed to try this and must say I am impressed how fast it is. Like the drag ‘n drop feature, the plugins section. In short, finally a complete and fast text editor.

  67. The LaTeX highlighting is subpar. Just compare to the Sublime with the Monokai theme, especially in the math environments.

  68. Like: lots of little editing features
    Improve: don’t replace path/filename (which contains/is symbolic links) with real path/filename when opening a file
    I’m actually using Kate 17.12.3.

  69. Is it about some missing actions to fold e.g. then 2nd level or so? Could you list all this?

    It is sad to see that everyone only complains, but no one steps up to send a patch. How can that be?

    1. Yeah, write a patch, so someone could obliterate it again due to ‘cleaning up interface’ (the actual reason to cripple code folding) and then pretend the problem doesn’t exist for another six years or so (like it was with code folding).

      Funny enough, I still use Kate, but I had to do bunch of scripts around it to make internals of PHP class look like top level code, create multiple backups with dates added to filenames (and moved to a special backup directory), etc. But I’m getting tired with all this, and I will probably jump the ship (np++) the moment another problem surfaces. Actually, there are already two problems that are slowing me down (no hints for function calls, no autocomplete in large source files), but I’m bit too lazy to change the editor just for that.

    2. Okay, I think I see what wolfgang meant, because suddenly my Kate started to misbehave with code folding (I work on Neon distro). If code block is indented (like by one tab), folding a php function makes it occupy two lines (second one has a single ‘}’ character). Non-indented block folds to single line as before. This happens also in kwrite and kdevelop (that actually has function hints I was complaining about before – my bad). This is especially painful, because I think I would be a die-hard kdevelop user. Instead, I just moved to np++. Tried atom, but this is even worse: lots of bugs (usually ending in php displayed as plaintext) just openly ignored by developers (‘nofix’).

      I’m really sorry I finally was forced to leave Kate. What a shame.

    3. Forgot to mention – apart from that one/two line function folds there can be random folds or non-folds inside the functions and it seems there’s no way of forcing Kate to display it correctly, like this was locked in some way. My suggestion: if you really don’t have manpower to reanimate Kate’s code folding or incorporate some external engine like scintilla, just redo this into indentation-based folding. Maybe not perfect, but at least usable.

  70. Tell me: Is it really necessary to use code folding? I am especially interested in an answer to this question since I have a degree in computer science–though I’ve never worked in the field and, these days, do not code. But, if I were to code, I likely would just use Kate’s excellent bookmarking ability to instantly move around huge files of code. I fail to see what the big deal is. Wouldn’t Kate’s excellent bookmarking facility be enough to easily navigate code? Back in the day, there was no code folding, and we did just fine without it.

    1. I use code folding since late 1980s when it was introduced in GFA Basic (on Atari ST, currently it is known as X11 Basic), so ‘back in the day’ is what – single line editor (like before vi)? Anyway, GFA editor could fold procedures/functions only (exactly what I need now). It looked like upside-down Nano, except it also instantly enforced valid syntax, did full auto-indentation and supported shortcuts for commands (for example if you typed ‘n a’ it was automatically expanded into ‘NEXT a’. So in that regard Kate and other IDEs are still behind this old tiny editor.

      Before that I did mostly assembly, so really I’m used to various styles of coding, yet I find folding a very important feature that makes it easy to efficiently navigate between portions of code you need to work on at the moment. In case of Kate it is not only folding, but also the document map and red/green line markers that show what was edited in current session. These 3 features make Kate brilliant (you save hours of non-essential clicks, scrolls and keystrokes), but lack of usable folding is a deal breaker.

      In np++ I’m using now there is a document map and the line markers as well, but you have to scroll that map (Kate scales it to fit), and markers on that map don’t agree with fold state, so I don’t use these features, yet I chose np++ because of folding.

      AND finally – every decent code editor supports that feature, so probably there must be something to it… (:


Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top