Dmytro Maluka

@zyedidia what do you think about this?

I'm still using it all the time. If you feel like compiling micro yourself, you can also pull this PR and try and use it. @zyedidia Any chance you review...

I consider trailing whitespace an error too, so tab errors are just a special case of whitespace errors. Or are you suggesting to combine both options into a single option,...

> If we consider something as an error, we shouldn't reproduce that error but auto-indentation just copies previous line indentation Shouldn't we? Consider such a code:  The `for` loop...

Rebased on top of the newest master (just to clean up the commit history, no functional changes).

I think this behavior is not intended, and it would be good to fix it. The problem is that it is not quite easy to fix. For parsing command-line options...

> it is a strange design for configuration files. Yes, it is. If I was @zyedidia I would design it differently. But we can't just change it now, since we...

> As a partial workaround we can (can we?) not to rewrite bindings.json if nothing differs so if bindings weren't changed by plugin, user at least won't see annoying "file...

This can be already done using Lua. You can try adding this to init.lua: ``` local util = import("micro/util") function preCursorLeft(bp) return bp.Cursor.X > 0 end function preCursorRight(bp) return bp.Cursor.X...

I was going to say "yes", but I've found that micro currently supports turning options on/off via command line (`micro -option`) for its built-in options only, not for options provided...