Live data from Hacker News

Kate editor on all platforms

cullmann.io

131–140 of 159 posts

Re: Kate editor on all platforms

#131
post #109

Earlier quoted context omitted.

That sounds more like switching to macos being terrible. If I am used to kate on linux, windows,..., then I expect it to just work if someone hands me a mac with kate. If you additionally want mac-style shortcuts as an option that is fine, but defaults should be consistent.

There's no app that uses the same shortcuts in all OSs because that's just stupid (amongst other reasons, because the shortcuts would conflict with the OS's own shortcuts, just to mention one obvious reason). You need to default to the OS's defaults, and maybe have an option to try using another OS's defaults (like other IDEs do).

Let me just call bullshit on that

https://support.google.com/chrome/answer/157179?hl=en&co=GEN...

Wow, ctrl+p instead of boxy thing+p, such difference.

Re: Kate editor on all platforms

#133
post #94

It’s been a long time since I have used Kate. I see it is stealing design elements from VSCode just like JetBrains UIs decided to. That really disappoints me. I really don’t get the point of doing so. If I wanted to use VSCode, I’d use VSCode rather than the knock off. Why not have a distinct visual identity for crying out loud.

because its not very easy to come up with new designs, at least for me. On the other hand if another tool provides a good and easy to understand UI, copying it makes sense. Kate still has a lot of its own things and ideas.

Re: Kate editor on all platforms

#134

Kate is a lovely editor. I wrote about half of Designing Sound with Kate before switching to Emacs near the end (to better handle code integration). What I appreciate is the ability to have a pane of files open and very quickly cut and paste between them. Even though I am a baptised and confirmed Emacs disciple, I still never find the buffer orientation quite maps to files the way I want. Kate hit that sweet-spot in…

Kate has good code integration these days, but it depends on the language. Might not be great for some languages.

Re: Kate editor on all platforms

#135

Earlier quoted context omitted.

Simple reason: Because the package is not optimized for that. It can be shrinked more, but that needs help. And I must confess, I rather spend my time on bug fixes than space optimizations.

Hey, Kate is awesome! Didn't mean to bring you down or anything. I myself got some trimming to do for my own apps. Keep up the good work. BTW, any idea how Kate is so fast? Is there an architecture explanation somewhere? Is it based on Scintilla? I'm on a block editor[1] in Qt C++ and QML so that kind of information will be helpful. [1] https://www.get-plume.com/

the architecture is really simple. The buffer contigously stores a list of "blocks". Each block contains a small number of actual text lines (usually 64-128). Thus if you edit a line, we only need to update the block containing the line. Once a block grows bigger than a certain number of lines, we split it into two.

Re: Kate editor on all platforms

#136
post #92

I logged in solely to say that Kate was the main reason I stuck with KDE as my desktop environment, back in the KDE 3 days. I switched to Mac some time ago but I still use Kate as my editor. I'm happy that it still exists.

Kate on MacOS is terrible. I've tried helping them fix the shortcuts which are all "wrong" (MacOS uses certain shortcuts that are unlike most Unix systems, but Kate doesn't actually use the right ones all Mac users expect so it's a nightmare until you manually override at least some of the shortcuts yourself). I tried using the build tool (suggested in the article) but building Kate was a nightmare even with that...…

IIRC, you came around in the kate channel on the matrix. Unfortunately you gave up really close to getting the build successful :)

I did try to help as much as I could, but I am no Craft expert myself and we were transitioning to Qt6 at that time so things were more difficult than usual. Should be a lot easier now I think if you want to try.

Re: Kate editor on all platforms

#137

Earlier quoted context omitted.

Hey, Kate is awesome! Didn't mean to bring you down or anything. I myself got some trimming to do for my own apps. Keep up the good work. BTW, any idea how Kate is so fast? Is there an architecture explanation somewhere? Is it based on Scintilla? I'm on a block editor[1] in Qt C++ and QML so that kind of information will be helpful. [1] https://www.get-plume.com/

the architecture is really simple. The buffer contigously stores a list of "blocks". Each block contains a small number of actual text lines (usually 64-128). Thus if you edit a line, we only need to update the block containing the line. Once a block grows bigger than a certain number of lines, we split it into two.

Hey, Waqar!

If I’m not mistaken, you also contributed to my own Notes app https://github.com/nuttyartist/notes, so thanks!

Can you please point where in Kate’s source code I’ll see the implementation for this? That would be super helpful.

Re: Kate editor on all platforms

#138

Earlier quoted context omitted.

KDE4 ruined Amarok too. That's why there's Clementine and Strawberry now, which are forks from Amarok 1.4.

Amarok did 'die' because the dev team dissolved due to multiple issues.

Huh, interesting. Well it still supports my point that when people looked to which version to resurrect, they did not pick Amarok 2.

Re: Kate editor on all platforms

#139

Earlier quoted context omitted.

KDE4 is a sad story. It ruined the reputation of KDE for a very long time. I loved KDE 3.5, but then came back to KDE only in 2021. It's mostly just a problem of communication. KDE 4.0 should not have been marked as stable and should not been used by distros. If they baked KDE4 for two more years and on the side maintained/developed 3.5, the transition might be much smoother.

While there were some bugs in early KDE 4, those were not the main problem. No amount of baking could have saved it. The main problem was caused by the completely different purposes of the new developers, who have removed all the outstanding customization features of KDE 3.5. For me, indeed KDE 3.5 has been the best graphic desktop that I have ever seen. Neither before, nor after and neither on Apple or Windows have…

Another problem with KDE 4 was the buzzword technologies pushed everywere - semantic desktop with Nepomuk (nice research project but not fit for normal use), plasma applet UI added to applications (why?), activities replacing virtual desktops but not really.

Re: Kate editor on all platforms

#140

Earlier quoted context omitted.

KDE4 ruined Amarok too. That's why there's Clementine and Strawberry now, which are forks from Amarok 1.4.

Amarok did 'die' because the dev team dissolved due to multiple issues.

Amarok became unusable with KDE 4 before it died.
Post reply on HN