Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How I use Kate editor

akselmo.dev

Post reply on HN
Print view View original

71–80 of 88 posts

Re: How I use Kate editor

#71

Post by cirwin »

tasuki wrote: post #66
cirwin wrote: post #43

Earlier quoted context omitted.

Zed maintainer here. We use node.js to run a number of language servers and formatters (which are often written in node due to the VSCode ancestry...). There've been a lot of requests to disable language servers by default; but I think that's not the right default for most users – things should work out of the box. That said, better control over this is definitely something we will add.

Is it true Zed downloads node.js as a binary from the web? Why wouldn't you use the system provided node or package it with Zed if it's necessary?

We currently download node if the system version isn't recent enough (we used to always download it, but I fixed that...).

Re: How I use Kate editor

#72

Post by peppers-ghost »

tux3 wrote: post #6

If 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…

Thank you for this!

Re: How I use Kate editor

#73

Post by bradrn »

levodelellis wrote: post #48
HexDecOctBin wrote: post #28

One feature that is impossible to live without for me is Undo Tree. Unfortunately, the only editors that support it are Vim/Neovim and Emacs. I would love to switch to one of these modern editors, but not a single one of them supports this feature.

I'm writing an editor. Could you explain to me the use case? I looked it up and I don't exactly understand the reason besides it might be fun to look at I really did not like that other editors would lose text if you pressed undo and type. The way my undo's work is if you type "a b c" and hit undo twice (so it's just "a") then type "d", then undo twice, it'll restore to "a b c"

If I understand correctly, this is the same as the default behaviour for Emacs (on top of which Undo Tree is implemented).

Re: How I use Kate editor

#74

Post by dr_kiszonka »

bogwog wrote: post #23

This is pretty much the exact same way I use Sublime (except the git diff stuff is done in Sublime Merge, which is a separate application) I've tried switching to Kate a few times since I prefer open source tools, but it feels like a major step down UX-wise. My primary workstations have been Linux with KDE Plasma for many years, but I am not a huge fan of the KDE aesthetics (which seems to aim for maximizing clutter)…

I like that you can extend Sublime with Python. I know that it will never be Emacs, but Emacs is too hard for me, while Sublime feels much more accessible.

Re: How I use Kate editor

#75

Post by [deleted] »

matthewmc3 wrote: post #36
tux3 wrote: post #27

Earlier quoted context omitted.

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.

[deleted]

Re: How I use Kate editor

#76

Post by larusso »

bigstrat2003 wrote: post #21
larusso wrote: post #8

I‘m contemplating for a while to find a replacement for VSCode. I switched to it because Atom became too slow and it had great builtin support for most stuff. But I actually was never 100% happy. I usually split my work between bigger projects and smaller file edits. And VSCode was good for the second flow. But over the years and the popularity of LSPs it kinda became dump as well. I mean the fact that if one wants t…

Haven't used Kate, but I strongly recommend Sublime Text. It's lightweight and the plugin support means you can add more features if you need them.

I used sublime before and was happy enough. But the license thing never sit well with me.

Re: How I use Kate editor

#77

Post by actuallyalys »

shmerl wrote: post #33
actuallyalys wrote: post #4

I 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.

I should honestly give DAP a try in Neovim. I think DAP being newer, seemingly getting less attention than other elaborate technologies to integrate like LSP or Treesitter, and having a more complex UI made me suspect it might not be reliable. Adding a DAP plugin to a secondary editor also feels less risky. But it sounds like my concerns may have been addressed, if not overblown all along.

Re: How I use Kate editor

#78

Post by actuallyalys »

nartho wrote: post #16
actuallyalys wrote: post #4

I 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.

Have you tried zed ? I have been really impressed by it.

Fasterthanlime recommended it a while back on Mastodon so that did pique my interest. The focus on AI kind of put me off Zed, though. I don’t know whether that’s fair—I see one of their blog posts touts “Out of Your Face AI”—but that was my reaction.

Re: How I use Kate editor

#79

Post by shmerl »

actuallyalys wrote: post #77
shmerl wrote: post #33

Earlier quoted context omitted.

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.

I should honestly give DAP a try in Neovim. I think DAP being newer, seemingly getting less attention than other elaborate technologies to integrate like LSP or Treesitter, and having a more complex UI made me suspect it might not be reliable. Adding a DAP plugin to a secondary editor also feels less risky. But it sounds like my concerns may have been addressed, if not overblown all along.

If you worry about it interfering with other stuff, you can lazy load nvim-dap + nvim-dap-ui on demand (using lazy.nvim for example), but it's not really interfering with what I use in my experience.

Plus I use sessions for key mappings, i.e. temporary sets of mappings used for debugging for example, which can be reset to what they were after debugging is finished. This way you can assign a bunch of common combos for stuff like step in / step out without it messing up other existing mappings which you can restore after you are done.

Re: How I use Kate editor

#80

Post by badsectoracula »

slightwinder wrote: post #69
badsectoracula wrote: post #34

Earlier quoted context omitted.

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 ...and watch Kate struggle with a ~100KB file. It seems to be related to the text layout or something along these lines (i.e. it isn't because of whatever data structure it uses for text, modern PCs should be able to handle the naivest…

> ...and watch Kate struggle with a ~100KB file What do you consider as struggle? Here this works fast and flawless with Kate, VS Code, vim... Though, I did not use /tmp, but $HOME. But I doubt this would make a difference, unless your KDE is broken and Kate struggles because of kio on opening the file.

> What do you consider as struggle?

Choppy scrolling, taking up to a second to add a line in the middle of the text, etc. As i wrote, the issue was with scrolling and adding/removing lines - so most likely text layout stuff. The file I/O was fine.

Post reply on HN