zyedidia

Author here. I think there is definitely room for improvement in the iterator API. I intend to experiment with more implementations in the coming weeks with the goal of settling on something better by the time Go 1.18 is released. The main alternative I have in mind is a cursor-style iterator (for example, with `Next`, `Done`, and `Value` methods). If you have something else in mind too, let me know and I might be able to try it out.

Yeah that's a drawback -- multi-cursors will be displayed as blocks regardless. As far as I know there is no way to solve that, but using block cursors for multi-cursor operations isn't that bad.

Sure you can, but you have to use a trick. You can fake it by modifying the background color of the cell where the cursor is located. Many terminal editors have support for multiple cursors.

Did they just appear as space characters, or did they actually not take up any cells in the editor? Currently some non-displayable characters are rendered as spaces, which is not ideal. I will look into displaying non-displayable characters in a special way (perhaps as `^@`, similar to how Vim does it, or with �, which is meant for this purpose).

Thanks for finding that! I have fixed the two issues (file not getting saved, and syntax highlighting not updating). Please open a Github issue if you find any more like those.

Mostly so that I can use Vim keybindings with micro :). Hopefully after improving the keybinding system, it will be fairly easy to implement a Vim plugin, so it shouldn't take much time. Of course, the Vim plugin will be optional and not provided by default, but I think it would be nice to have, and would make me more efficient with micro.

Despite the sassy response in the FAQ about Vim keybindings, I am planning to implement Vim keybindings for micro in the next version, along with an improvement to the keybinding system in general. Stay tuned for 2.1.0 which I hope will include this feature.

Do you remember what version that issue happened on? Were you using unicode characters or a non-UTF8 encoding? That sounds like an annoying issue and it would be great to fix it.

Yes it's unfortunate that there is already a popular Go project called "micro." The name here is a play on "nano" editor and I had already started the project by the time I saw https://github.com/micro. Oh well, I still like the name.

Unfortunately it is impossible to bind the mac command key because the terminal does not forward those key events to the applications (for example pressing Cmd-Q closes the terminal, not the app running in the terminal). See this issue: https://github.com/zyedidia/micro/issues/19.

I know people for whom Vim was overwhelming to learn and they gave up or didn't use it properly. I'm trying to make an terminal-based editor which gives them as much as possible of the power of Vim or Emacs, while making it dead simple to learn and use.

The reason I do the check that way is because if the user adds a character, and then deletes it, the buffer has not been modified, but if you just set a bool to true when an insert event happens, it will think the buffer has been modified.

If there is a better way to do this please let me know.

In addition to those features, micro also supports colors better. You can make colorschemes for it so that syntax highlighting is consistent across filetypes, and it supports 256, and true color, while nano only supports 16 colors.

Micro can also easily interface with the system clipboard (Ctrl-c, Ctrl-x, Ctrl-v).