Live data from Hacker News

Writing my own text editor, and daily-driving it

blog.jsbarretto.com

111–120 of 124 posts

Re: Writing my own text editor, and daily-driving it

#111

Earlier quoted context omitted.

I'm curious, how old do you think I am?

Oh damn, I very much misread your message as "I'm 19 and using my own-" Yeah, okay you have 10 years of dogfooding ahead of me X) Sorry. Still, goals.

They could've started writing it in the womb. I don't think you were categorically wrong...

Re: Writing my own text editor, and daily-driving it

#112

One of the best kept secret and one that he should have tried is "Kate". Good old style editor that is a native app, not an electron app. All the features that you might want and more, but simple and efficient. And the most important for me, super snappy. I can't bear the latency that you get for typing code when using things like vscode. I don't know how people can appreciate that.

Kate is the editor i'm using these days on Linux (even though i use Window Maker for my WM and not Plasma) but it does have a few weird aspects. One of them, which annoys me, is that every "tab" is really its own entire editor with its own state - if you do something like search for a word in one file then switch to another tab, you can't use F3 to search for the same word again in that file because that's actually a different editor and it doesn't know that you searched for something in the other tab. This extends to other stuff, as if the main Kate window is just a window manager for the editors it launches in it and it just pretends the UI is shared.

Re: Writing my own text editor, and daily-driving it

#113

Earlier quoted context omitted.

I'm quite partial to Zed. Very snappy, and you can turn off all the AI features globally if you like.

Zed is a no go in my book until they learn to respect their users and stop installing third party software* without asking. Completely unacceptable practice, and their reason of "most people will want LSPs to be there without effort" doesn't cut it. * nodejs specifically, but it wouldn't be ok no matter what the software was. It's my computer, not yours, don't download and run stuff without getting permission.

I get where you're coming from.

But what percentage of users of a document editor would say "don't install pdf stuff on my computer without asking, I don't need to export to pdf"

Installing dependencies for popular features is very much the norm. It's mainstream software.

The same complaint would be made for VSCode and Jetbrains - the most popular IDEs

Re: Writing my own text editor, and daily-driving it

#115
post #53

Earlier quoted context omitted.

You can already do this in vim. Pretty easy to shell out to whatever command you want and use the result for various purposes.

That's still built on top of the hardcoded vim design choices though. For example, I really like the "select then edit" approach of Helix, but Vim doesn't really play nice with that (there may be better plugins since I last looked to be fair). File handling, buffer rendering, and frames have very little to do with that, and yet I have to switch editors, lose all my plugins and configurations, and switch all those sub…

You're right that changing the whole editing model will involve rewriting a lot of keybindings. You could do that in vim if you really wanted to -- start by remapping motions to enter visual mode first. I don't really know why you'd want that when visual mode is already a keystroke away, but that's ok.

FWIW though if that's what's important to you, I get the sense that kakoune is much more vim-like in making it easy to compose with other tools, while being set up for your preferred editing model.

Re: Writing my own text editor, and daily-driving it

#116

One of the best kept secret and one that he should have tried is "Kate". Good old style editor that is a native app, not an electron app. All the features that you might want and more, but simple and efficient. And the most important for me, super snappy. I can't bear the latency that you get for typing code when using things like vscode. I don't know how people can appreciate that.

I know this is just one data point, but I don't notice any latency when typing code in VS Code. It takes a while to start up, and that is annoying especially for quick short editing jobs, but other than that I never notice any sluggishness. Is this something many people experience?

I can tell for you specifically because everything is specific: machine, hardware, setup, projects...

But I always noticed this latency for everyone I ever saw using vscode or computer that I tried.

To be clear, you might easily not notice it if you are used to that and don't know better. And it is consistent with most electron based apps or editors. But there is a very subtile latency between the time you hit the key in the keyboard and the time that it appears on screen. Basically you are typing letters a little bit in advance. With Kate it is like with a basic text edit, characters appears instantly.

The effect is the same when you type anything in web browsers. In form, editor or whatever.

Re: Writing my own text editor, and daily-driving it

#117

This was so nice to read, I've been trying to encourage my friends to write their own editors, there's something really nice about the process of working within your own tool. I've used my own text editor(it's call Left) for nearly 10 years, it took time to get it just right, but I iterated over the years(using Left to edit Left) but that time I spent putting it together is paid back 20x by the joy it gives me openin…

Indeed - I've been using my personal editor for over a decade now. It's a good and comfortable feeling to spend your work day in a tool which fits you perfectly.

Re: Writing my own text editor, and daily-driving it

#118

I laughed out loud when the author wrote 'it replaced nano'. So you are claiming to have tried dozens of editors, discarded them, only to land on nano as your daily driver? If that's true, this person must be a character.

He implied replacing nano was the first step, before using it for more complex (software development) tasks. First use it just for quick one-off edits of /etc/blah.conf then graduate to using it for longer editing sessions.

Re: Writing my own text editor, and daily-driving it

#120

I laughed out loud when the author wrote 'it replaced nano'. So you are claiming to have tried dozens of editors, discarded them, only to land on nano as your daily driver? If that's true, this person must be a character.

No, nano is not my daily driver. It's what I use when I want to quickly edit a file with root access because, funnily enough, I'm not in the habit of running my primary editor with superuser permissions :) Nano is a low-hanging fruit that was the first of many tools I gradually massaged the editor into replacing.
Post reply on HN