Why does :q kill my emacs?

Wed Jan 26 11:56:03 CET 2011

 Hi Titus

> When coming from Vim, you're used to have many Vim instances which you

I'm coming from Vim (MacVim now, but on Ubuntu before, and before that
on MS*) and I used to have a gvim window that I used for all my edits,
using tab and window combinations and remote-silent-tab stuff etc.

So I seldom did quit the Vim session, only buffers within it.

> often quit.  When working with Vimpulse and emacsclient, you have one
> emacs instance instead and the pattern to use :q to close files
> doesn't make much sense anymore.  But I'd prefer to learn using :bd or
> C-x # over redefining :q to mean something else than quit.
>
> Apart from that, if :q kills only a client, what would you use to quit emacs?

Who wants to quit emacs as a common task. Isn't this the thingie that
yoou start automatically and stays alive for all your editing,
directory browsing, eshelling etc...

I rarely quit Emacs, but I frequently want to save and quit a buffer,
so I prefer the viper way to do this in one sinle :wq command and I do
think that it would be nice of this was combined with server-edit
so that I even don't need to think about quitting differently if I am
editing as a client to e.g. my gmail.

I wouldn't mind to use C-x C-c to quit emacs on the rare occasions
that I want to quit emacs.

Guivho.