On 11/30/2012 12:13 PM, Igor Stasenko wrote: > well, what you explaining here is not just about handling keyboard > typing, but also > requires changes in UI (showing command line, black & white color > scheme, 80x25 text mode ;) ) etc..
I know you're joking, but limiting one's self to 80 columns is generally a good way to maximize screen space. Step back and look at code that runs with really long lines, and you'll see a vast emptiness on most lines. > i think, if vi would contest for "best obscure editor", i guess it > would get 1st prize. i don't really care why you like it , just can you > (or someone else) explain me, why you think it is best possible way of > doing things? Since i can't see it. Monkey-bopping not a compelling argument? I mean, the goal is to make a fluid interface. The subtitle of one of the vim books is "Edit at the Speed of Thought". That's the key thing. When I'm coding with vi keys, the text just goes where I want it, and quickly, with very little stopping to think about it. > What exactly commands/shortcuts you wanna have there? > And wouldn't it be better to focus UI design towards avoiding the need > for shortcuts/modes alltogether? Possibly. I'll think about that. > After all, you can run vi/emacs/<put your favorite> in separate window, > and can always copy-paste text between, and enjoy your lovely keyboard > shortcuts. This is something that Pentadactyl (a amazing Firefox plugin that makes the browser vim-like) does. You can hit Ctrl+i on any text field, and it pops up a gvim window with that text. Perhaps something like this is sufficient. We'll see. My problem right now is that I have dozens of projects that steal my free time from getting into Smalltalk, but I'll fix that as soon as I can. —☈
