Re: Back to emacsclient/server

[Stefan Monnier]

> Isn't it better to start with a well known number and if that is busy, just
> add 1 until you get a free one?  That way emacslcient can have a default which
> just works if there is just one emacs server running.

Huh?  Why would you need that.
It seems just as simple to
- bind to any port.
- get the port that was used.
- write it into ~/.emacs.d/server/server ("server" is the default
  `server-name') along with the host name and the auth key.

emacsclient looks in ~/.emacs.d/server/server (where "server" is the
default but can be changed with --server-name) to find all the relevant info.

> Emacsclient by default then reads ~/emacs.d/server-0.  emacsclient --server 1
> would be ~/emacs.d/server-1.

That sounds messy.


        Stefan