[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: w32 does not have emacsclient/server

From: David Kastrup
Subject: Re: w32 does not have emacsclient/server
Date: Sat, 06 Aug 2005 14:43:44 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Juanma Barranquero <address@hidden> writes:

> On 8/6/05, Eli Zaretskii <address@hidden> wrote:
>> I'd say, if no one posts any practical comments in a week or so, go
>> ahead and commit the changes.  After all, the Emacs development rules
>> do not mandate any peer review at all.
> You're right.
> I would've liked some comments, though, for two reasons:
>   - It's an incompatible change, if small: --socket-name does not
> exist, and you *must* use either the EMACS_SERVER_FILE environment
> variable or the --server-file argument to emacsclient; otherwise
> emacsclient will refuse to work.

Uh what?  Isn't there a default file name?

>   - I've been vocal in stressing that I think our freeze is not very
> cold at all. So I'd like someone with a more objective POV to decide
> whether this (making emacsclient/server work on Windows and from
> remote machines) is a bug fix or a new feature.

It is a new feature fixing a bug.

> Of course I'd like to include it now, but I won't complain if the
> decision goes to shelving it for the moment being.

In my opinion it is one thing worth the hassle of ironing out, though
it is definitely new.

David Kastrup, Kriemhildstr. 15, 44793 Bochum

reply via email to

[Prev in Thread] Current Thread [Next in Thread]