|
From: | Lennart Borgman (gmail) |
Subject: | Re: EmacsW32 invocation options |
Date: | Wed, 02 May 2007 17:03:46 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666 |
Juanma Barranquero wrote:
Yes. I think that's the main problem. There was no need to rush that. It is nice for emacsclient to be able to start the server, but it is not a pressing need. The alternative is a few more clicks every now and then (not each time emacsclient is run).
I was concerned about new users. Every difficulty when trying to start using Emacs is a big thing. And if you are on MS Windows it was very difficult to get started.
I also added a switch --server-file FILENAME for which I wrote "Set filename of the TCP authentication file".You must be talking about some other thing. IIRC, I added that switch:
Eh, yes you are right.
I'm not keen on rehearsing the discussion; I think there's not one single way to start the local server. A way to pass that setup info is needed.
I am sure there is more to know about that than I do. However if you are talking about user specific elisp code that must be ran I believe it is possible to extend the solution in my patched Emacs client without difficulties.
[Prev in Thread] | Current Thread | [Next in Thread] |