[Top][All Lists]

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

Re: starting emacsclient with emacs --daemon

From: J. David Boyd
Subject: Re: starting emacsclient with emacs --daemon
Date: Thu, 30 Jan 2020 12:42:14 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (cygwin)

Eli Zaretskii <> writes:

>> From: (J. David Boyd)
>> Date: Wed, 29 Jan 2020 13:06:39 -0500
>> >> Sorry.  Emacs 26.3, under Cygwin running under Windows 10.
>> >
>> > Thanks.  But this still leaves a bit of uncertainty: there are 2
>> > Cygwin builds of Emacs -- one needs an X server, the other uses the
>> > MS-Windows (a.k.a. "w32") GUI toolkit.  Which one do you use?
>> Yes it does.  :-)
>> I'm using the version that runs natively - /usr/bin/emacs-w32.exe
> OK, thanks.  I suspect that what you see is due to a change we madde
> in Emacs 26, which was found to cause too much trouble, and thus was
> reverted for Emacs 27.  So I suggest to try a snapshot of the Emacs 27
> codebase, this problem might be fixed there.

Thanks so much for your info, but it turns out the problem was between my

Once you mentioned the 2 versions of emacs, one for X server, one for native,
that struck a chord.

So I went back to the X server version, and emacsclient -c -n works just fine
there.  I was thinking that something had changed in emacs, but instead I had
changed the very emacs I was using.

Sorry for the bother, I can live with emacs working as it does under Cygwin
with the native version.  I just didn't understand what had changed.

Thanks again!

Dave in Hudson, FL

reply via email to

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