🚀 go-pugleaf

In article <jimhill.835463897@kitsune>,
	jimhill@swcp.com (Jim Hill) writes:
|> changj@jeff-lab@queensu.ca (Jianlin Chang) writes:
|> 
|>>I am considering learning emacs after using  vi for a long time. Is
|>>the time spend on learning really worth the benefits of emacs vs vi?
|>>Thanks a lot.
|> 
|> Sure.  The power and flexibility that emacs gives you makes it well
|> worth knowing.  That said, I'm having a hell of a time making the switch
|> myself because editing in vi requires no conscious effort.  My emacs
|> documents tend to have a lot of jjjjj's or :wq's in them just from force
|> of habit.
|> 
|> The hardest part of making the switch, at least for me, is not trying
|> to learn/remember all of emacs's commands; there are only a handful
|> that you _need_ to know upfront.  The hardest part is overcoming the
|> subconscious.
|> 
|> Jim
|> -- 
|> jimhill@swcp.com                          http://www.swcp.com/~jimhill/
|> 
|>    "Iced tea keeps me in a summertime frame of mind."  --  Meldrick Lewis

I too think it is worth the time learning emacs. I've got the version
for X-windows, with the menubar on it, which is great when learning
all the different things :)

The biggest problem I had was indeed finding out this handful of commands
which are essential. Maybe this is a good question for the FAQ:
what are the basic commands one needs to know, before one can use emacs?

An answer could be:

C-x C-f   load file
C-x k     kill buffer
C-x C-s   save file
C-x C-c   quit emacs
C-s       Search
C-h b     list key-bindings
C-h a     command apropos


Well, these are the commands I learned to use first YMMV.



Andries

-- 
------------------------------------------
Andries Kruithof         kruithof@slb.com
Geco-Prakla  
Kongeveien 79, N-3196 Horten (Norway)

These opinions are my own, not necessarily
those of my employer
------------------------------------------