on iPhone Safari i don't get the grey middle background layer, only dark text on dark background
Writing my own text editor, and daily-driving it
21–30 of 124 posts
Re: Writing my own text editor, and daily-driving it
#22[dead]
Re: Writing my own text editor, and daily-driving it
#23Earlier quoted context omitted.
It's not that bad. You need really large files to notice. The largest realistic file I'll ever touch - sqlite3 amalgamation with 270k lines and 9.1 kB - still takes only 6 ms to memmove it on my poor laptop. Any regular up-to 10k lines file is memmoved in order of microseconds.
That's true for code editing, but it's nice to not have to reach for a different solution when editing huge files. Sometimes I like to open up big log files, JSON test data, etc.
Do you actually edit big log files?
Re: Writing my own text editor, and daily-driving it
#24[flagged]
Re: Writing my own text editor, and daily-driving it
#25[dead]
Re: Writing my own text editor, and daily-driving it
#26I use my own text editor too. Nobody else seems to get value from it. I’m still surprised by the value we get from home grown solutions.
I use my own editor too. I modified an existing editor to my own needs. But I do use VSC as well for multi file projects. My editor can load images as well and has a scripting language to manipulate images. I primarily use it to edit my website, which is a static website in bare HTML. It also has some 'browser' functions in the sense that F5 opens a link including jumping to an anker if there is one in the link. It does have colour coding for HTML that also checks for matching tags.
Re: Writing my own text editor, and daily-driving it
#27I, too, mourn the death of Howl. It was a quirky yet surprisingly "comfortable" editor.
But I am now at home with Helix and Flow Control.
Re: Writing my own text editor, and daily-driving it
#28I use my own text editor too. Nobody else seems to get value from it. I’m still surprised by the value we get from home grown solutions.
I use my own text editor too, written using my own programming language. Fortunately Operating Systems suit my needs and I won't have to write my own OS ;-)
Re: Writing my own text editor, and daily-driving it
#29Earlier quoted context omitted.
It's not that bad. You need really large files to notice. The largest realistic file I'll ever touch - sqlite3 amalgamation with 270k lines and 9.1 kB - still takes only 6 ms to memmove it on my poor laptop. Any regular up-to 10k lines file is memmoved in order of microseconds.
That's true for code editing, but it's nice to not have to reach for a different solution when editing huge files. Sometimes I like to open up big log files, JSON test data, etc.
I am always surprised even vim chokes on files with one massive line. That could be a useful optimization too.
Re: Writing my own text editor, and daily-driving it
#30One 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.