The Atom code editor turns 1.0

Posted Jul 9, 2015 10:15 UTC (Thu) by nye (subscriber, #51576)
In reply to: The Atom code editor turns 1.0 by jzb
Parent article: The Atom code editor turns 1.0

>A lot of editors have vi- /Vim-like keybindings, but I've yet to find one that takes that far enough. Little inconsistencies are productivity killers.

I think the problem is that, when your editor was fundamentally never designed around the idea of fully composable commands, it's hard to retrofit them. This leads to lots of individual commands having to be added individually and it's impossible to implement all of the possible combinations that way.

Last year when I was first looking at Atom I read an article which discussed this pretty well: https://medium.com/@mkozlows/why-atom-cant-replace-vim-43....

The Atom code editor turns 1.0

Posted Jul 9, 2015 19:19 UTC (Thu) by drag (guest, #31333) [Link]

Instead of doing things like 'deleteLine()' it should of been 'delete(Line())'.

Then you can do things like add new functions that return regions of text or coordinates like 'EndOfLine()', 'BeginningOfLine()', 'ToClosingBrace()'. Then something like 'Lines($starting, $number_of_lines)', were the numbers number of lines can be positive or negative depending on what direction you want to go. Then the same thing for 'Words()' and 'Blocks_of_code()' and such things.

So you could do 'delete(Words(-2))'

Then for new language bindings they would need somebody to go through and define what a block of code is or what a word is and that sort of thing.