Re: Programmers Text Editor
On Tue, 6 Nov 2007 01:03:45 -0700
Nate Duehr <nate@natetech.com> wrote:
>
> On Nov 5, 2007, at 4:49 PM, Steve Lamb wrote:
>
> > David Brodbeck wrote:
> >> Using vi requires you to keep track of the
> >> editor's state in your head -- you have to remember whether it's in
> >> input mode or command mode. I've never been able to do that
> >> reliably.
> >
> > Neither have I. However I did learn early on in my vim life that
> > ESC in
> > insert mode puts you in command mode. ESC in command mode puts you in
> > command mode. So if you're not sure, just slap escape then you are
> > sure. :))
>
> I have an older friend who's been doing Unix since, well... the
> beginning, and we were talking about this once, and he pointed out
> that he and his buddies figured out the in all of the possible modes/
> windows, three ESC's would always get you back to command mode from
> "anywhere" in vi.
>
> I've never really analyzed that statement, but it did start me a new
> habit... I usually hit it more than once while/if I'm thinking about
> what to do next and know I need to go to command mode before doing it.
>
My problem is that half the time i hit f1 instead and go into help ending up
saving some change or other to the help file or something else, not sure what
and go into record mode, not to mansion that pasting always gives me crazy
indentations.
Personally I prefer emacs, but it takes longer to load and I am still looking
for a proper project management (find definition/declaration etc.). Tags always
seems to do something else then needed, especially with c++ and fortran (no
proper class support and people seem to think that fortran is not used by
anyone for some unknown reason and don't bother making editors work with it)
> --
> Nate Duehr
> nate@natetech.com
>
>
>
>
Reply to: