|
From: | Jan Djärv |
Subject: | Re: Back to emacsclient/server |
Date: | Mon, 23 Oct 2006 22:35:29 +0200 |
User-agent: | Thunderbird 1.5.0.7 (Macintosh/20060909) |
Stefan Monnier skrev:
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.
And if that fails, what do you do? You still have to handle bind failures.
- 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.
If you think so, I don't see much difference. Jan D.
[Prev in Thread] | Current Thread | [Next in Thread] |