Re: The emacsclient socket vs. etc/emacs.bash

[LENNART BORGMAN <lennart.borgman.073@student.lu.se>]

From: storm@cua.dk (Kim F. Storm)
Date: Friday, December 15, 2006 2:37 pm
Subject: Re: The emacsclient socket vs. etc/emacs.bash

> "Juanma Barranquero" <lekktu@gmail.com> writes:
> 
> > On 12/9/06, Richard Stallman <rms@gnu.org> wrote:
> >
> >>     - time 0: Emacs 1 starts its server.
> >>     - time 1: Emacs 2 starts its server, overriding Emacs 1's 
> server.>>
> >> Isn't that already a problem?
> >> Shouldn't we prevent this from happening, somehow?
> >
> > I agree. I don't like Emacs 2 blindly overwritting Emacs 1's server
> > (or socket) file.
> 
> I hate that too.
> 
> I typically have a "master emacs" instance running all the time.
> Sometimes I start another instance (e.g. in a terminal window)
> just to make some small change to a config file - and blammo - 
> the server is no longer associated with the master emacs.
> 
> But is this the right time to change this (it's been like that for
> ages).


This is one of the situation where it might be good to not have anything about server start in the startup files. If emacsclient starts emacs automatically then you do not need that.

Starting another emacs is then safe at least from this point of view.