The page doesn't say it, how well it handles very large files? Also, how does it handle editing files with various encodings? Asking this while having Notepad++ in mind.
How I use Kate editor
31–40 of 88 posts
Re: How I use Kate editor
#32Earlier quoted context omitted.
I also really like Zed. But what prevents me from switching to Zed, is my workflow. I tend not to run desktop GUI applications on my main development machine (headless and sometimes remote). nvim is excellent in such circumstances. Also nvim is available on all platforms. I know Zed is also recently available on Linux, but I really doubt it will be as good as Zed on Mac.
One of the biggest problems i have with running basic text editors like vim/nvim is the investment time to spin up a fully loaded workable development env; esp since i've never done it before. basic vim with some modifications in .vimrc is all i have and i know some of my colleagues are also this way! nowadays though i really want to use LLMs to write code for me instead of switching contexts on different platforms.…
Github copilot has an official [1] neovim extension. There are also third-party plugins for Copilot, Chat, Next edit etc.
Re: How I use Kate editor
#33I don’t think it will dethrone Neovim for me, but this makes me wonder whether Kate could become my second editor and allow me to largely drop VS Code, especially with the DAP support. The session support also looks interesting.
I use Kate only causally for some small temporary text snippets. I use Neovim with DAP fine using nvim-dap + nvim-dap-ui. I also recently started using LSP in neovim, and it's actually pretty powerful.
Re: How I use Kate editor
#34The page doesn't say it, how well it handles very large files? Also, how does it handle editing files with various encodings? Asking this while having Notepad++ in mind.
I use Kate all the time and IME it doesn't. In fact it struggles even with relatively small files. In fact try this:
seq -f"foo %100.100f" 1 1000 > /tmp/test1000 && kate /tmp/test1000
I'm only using for editing text files and source code so it rarely bothers me personally but it can be annoying sometimes.
Re: How I use Kate editor
#35Earlier quoted context omitted.
That is a lot of work just to use Dolphin. I daily drive KDE on my workstation and while it is not a terrible file explorer, I probably wouldn't go to those lengths to use it over Finder. Props for getting it done though, I didn't even realize it was possible. Makes sense though considering a lot of KDE apps are cross platform, like kdenlive.
In fairness, I wouldn't say it's dolphin I'm attached to in particular, I think I'm just not in the target audience for Finder. The tradeoff is that it makes simple things simple, and everything else complicated. I'm uploading a config file on a website. It's in ~/.config, and any reasonable file explorer won't show hidden files by default. In Finder there's also no button or setting to show hidden files. They really…
Just curious: how does drag & drop works with Dolphin in Mac? I quit KDE because I got mad with the files drop menu. Do you also get it when installing Dolphin?
Re: How I use Kate editor
#36Earlier quoted context omitted.
That is a lot of work just to use Dolphin. I daily drive KDE on my workstation and while it is not a terrible file explorer, I probably wouldn't go to those lengths to use it over Finder. Props for getting it done though, I didn't even realize it was possible. Makes sense though considering a lot of KDE apps are cross platform, like kdenlive.
In fairness, I wouldn't say it's dolphin I'm attached to in particular, I think I'm just not in the target audience for Finder. The tradeoff is that it makes simple things simple, and everything else complicated. I'm uploading a config file on a website. It's in ~/.config, and any reasonable file explorer won't show hidden files by default. In Finder there's also no button or setting to show hidden files. They really…
> You can't navigate to a hidden folder by typing its name (let's not get too creative!).
You can, actually. ⌘-SHIFT-G in Finder lets you navigate to any folder by typing in the path - even hidden paths. No mortal user would ever be expected to know or discover that, but it's there.
Re: How I use Kate editor
#37Earlier quoted context omitted.
Have you tried zed ? I have been really impressed by it.
I have tried zed, and promptly uninstalled once I saw it was automatically downloading and running nodejs. I want an editor that is lightweight, not one that starts running extra crap I neither need nor want in the background. That was on top of the big focus on LLM integration (itself already a significant negative for me), but which I was willing to overlook to try out the rest. I don't think Zed is very good in it…
Are you sure that was Zed? I see that it's 98.3% coded in Rust. But if you're right and it still depends on node.js, I'll have to scratch that off my list.
Re: How I use Kate editor
#38Earlier quoted context omitted.
One of the biggest problems i have with running basic text editors like vim/nvim is the investment time to spin up a fully loaded workable development env; esp since i've never done it before. basic vim with some modifications in .vimrc is all i have and i know some of my colleagues are also this way! nowadays though i really want to use LLMs to write code for me instead of switching contexts on different platforms.…
Github copilot has an official [1] neovim extension. There are also third-party plugins for Copilot, Chat, Next edit etc. [1] https://github.com/github/copilot.vim
It works with vanilla vim (and MacVim) these days too. "Vim 9.0.0185 or newer" is mentioned in the Getting Started section.
I was about to install it a couple of years ago, but then started thinking about the privacy threat model.
I realized that having a "copilot" in my everyday editor (not just for public open source coding!) is never gonna fly. I may end up accidentally uploading any file I open to a 3rd party for tab completion and "AI stuff". Even if I can configure it to hopefully ignore some directories, too risky for me. With a separate editor just for coding (Zed in my case), the risk of accidentally opening and uploading a wrong file would be much lower for me, as I'll keep using vim without any AI for everything other than OSS coding.
Edit: I'm sure there's an option only manually load the copilot plugin when you explicitly want it, but it still makes me too uneasy.
Re: How I use Kate editor
#39Kate's a pretty good editor. I've made an attempt to replace vscode/vscodium with it once before. The article is right about vscode turning into proprietary mush. I use vscodium and have run into issues with plugins that require cpptools, while cpptools complains whenever you, or an extension you're using, accesses it in an editor other than vscode.
how was your experience with kate as a full vscode replacement? anything major you missed or had to work around?
It's been awhile but I remember there were things I was used to, some really nice things, that I didn't want to give up.
I love vscode's markdown editing features. (pasting a link over text to create a hyperlink or dragging and dropping image files to embed images etc.) I think some of the keyboard shortcuts I was used to were different (duplicating lines, selecting all occurrences of a selected text). Behavior of word/token traversing(Ctrl + Left|Right Arrow) was different. There were some things kate couldn't do at all that I don't remember.
Re: How I use Kate editor
#40If you have an M3/M4 and are stuck on XNU like me, and you want a something between the notes app and a whole Electron IDE, it turns out that Kate also supporte macOS (Actually, a lot of KDE programs do, I was elated to find out I could use Dolphin as file manager when I was limited by Finder) I think Kate strikes this really nice middleground. It starts up immediately as just a text editor, but you can push it as fa…
It's in homebrew.
$ brew info kate
==> kate: 24.12,9168
https://kate-editor.org/
...