Live data from Hacker News

Micro v1.0 – a terminal-based text editor written in Go

github.com

41–47 of 47 posts

Re: Micro v1.0 – a terminal-based text editor written in Go

#41
post #7

8.5Mb is a little too much for editor named micro. Whole DD-WRT/OpenWRT Linux Image is twice smaller.

And kilo[1] is 28k but it doesn't have as many features. Also a "keyboard" vs "keystroke" editor, editors built before ginormous keyboards became ubiquitous use various keystrokes for commands, ones that came to exist in an assumed presence of a ginormous keyboard use special keys for commands. (example, if the only way to move the cursor up in your editor is the cursor up arrow key, you are a "keyboard" based editor…

That's weird, I didn't know keyboards used to be smaller. I assumed they started with the space cadet and kept shrinking.

Re: Micro v1.0 – a terminal-based text editor written in Go

#42

Earlier quoted context omitted.

And kilo[1] is 28k but it doesn't have as many features. Also a "keyboard" vs "keystroke" editor, editors built before ginormous keyboards became ubiquitous use various keystrokes for commands, ones that came to exist in an assumed presence of a ginormous keyboard use special keys for commands. (example, if the only way to move the cursor up in your editor is the cursor up arrow key, you are a "keyboard" based editor…

That's weird, I didn't know keyboards used to be smaller. I assumed they started with the space cadet and kept shrinking.

You are right, that isn't the correct analysis. Initial programming editors like EMACS, vi, EDIT, TECO, FINE, SOS, and KED tended to keep cursor motion and edit commands bound to key combinations that would be available on most (if not all) terminals. This minimized the use of "special function" keys, even if they were there, because they weren't there for all terminals. So the working set of keys was smaller even though the keyboards themselves were of nominally average size.

My observation was around the use of the PC's special keys used in "generic" editors because the authors of those editors have chosen to assume that everyone it typing on a keyboard that matches, or emulates, the 101 or 108 key keyboard that the PC made standard.

Re: Micro v1.0 – a terminal-based text editor written in Go

#43
post #21

Why does it seem like Go programmers need to include "in Go" on the tail end of product announcements?

Go is hype and people think that because it's done by google it's cool meanwhile people at Google are using more and more Rust they even made their own editor with it:

https://github.com/google/xi-editor

Re: Micro v1.0 – a terminal-based text editor written in Go

#46

First reaction: Congrats, looks great! Second reaction: Yet another, completely different syntax highlighting implementation/definition list... https://github.com/zyedidia/micro/tree/master/runtime/syntax Couldn't pick any of the hundreds that already exist? :(

What is the best syntax highlighting implementation/definition format out there ?
Post reply on HN