all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH 4/4] Fix emacsclient to work with cygw32
Date: Thu, 29 Dec 2011 20:18:59 +0200	[thread overview]
Message-ID: <83ehvnutpo.fsf@gnu.org> (raw)
In-Reply-To: <4EFCA9DB.3030002@dancol.org>

> Date: Thu, 29 Dec 2011 09:56:43 -0800
> From: Daniel Colascione <dancol@dancol.org>
> CC: emacs-devel@gnu.org
> 
> 
> [1:text/plain Hide]
> 
> On 12/29/11 9:39 AM, Eli Zaretskii wrote:
> >> Date: Thu, 29 Dec 2011 06:03:20 -0800
> >> From: Daniel Colascione <dancol@dancol.org>
> >>
> >> @@ -184,7 +188,7 @@ struct option longopts[] =
> >>    { "socket-name",	required_argument, NULL, 's' },
> >>  #endif
> >>    { "server-file",	required_argument, NULL, 'f' },
> >> -#ifndef WINDOWSNT
> >> +#ifndef HAVE_NTGUI
> >>    { "display",	required_argument, NULL, 'd' },
> >>  #endif
> > 
> > Maybe I'm confused: will HAVE_NTGUI be applicable to the Cygwin build
> > that can use the w32 windowing?  If so, it sounds like you are
> > creating here 2 kinds of emacsclient: one that can talk to a Cygwin
> > Emacs with X frames on another display, the other that cannot.  Why
> > cannot the same emacsclient work with both types of Emacs frames in a
> > Cygwin Emacs?
> > 
> > Apologies if I've misread the changes.
> 
> No, you're right.  I was following the template of the existing code
> here; IIUC, removing the conditional in the hunk above will let the same
> emacsclient talk to any kind of Emacs.

But the ifdef-out must stay in the native w32 build, I think, because
it causes trouble further down the line.  Juanma, can you comment,
please?




  reply	other threads:[~2011-12-29 18:18 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29 14:03 [PATCH 0/4] Support Win32 GUI in Cygwin Emacs Daniel Colascione
2011-12-29 14:03 ` [PATCH 3/4] Implement cygw32 Daniel Colascione
2011-12-29 17:29   ` Eli Zaretskii
2011-12-29 17:53     ` Daniel Colascione
2011-12-29 18:17       ` Eli Zaretskii
2011-12-29 21:50         ` Daniel Colascione
2011-12-30  0:56           ` Jason Rumney
2011-12-30  9:23           ` Eli Zaretskii
2011-12-30  9:36             ` Daniel Colascione
2011-12-30 11:16               ` Eli Zaretskii
2011-12-30  9:49   ` Andreas Schwab
2011-12-29 14:03 ` [PATCH 1/4] Compilation cleanups Daniel Colascione
2011-12-29 17:54   ` Paul Eggert
2011-12-31 14:50     ` Ken Brown
2011-12-31 20:29       ` Paul Eggert
2011-12-29 14:03 ` [PATCH 4/4] Fix emacsclient to work with cygw32 Daniel Colascione
2011-12-29 16:28   ` Juanma Barranquero
2011-12-29 16:36     ` Daniel Colascione
2011-12-29 16:43       ` Juanma Barranquero
2011-12-29 16:47         ` Daniel Colascione
2011-12-29 16:49           ` Juanma Barranquero
2011-12-29 17:39   ` Eli Zaretskii
2011-12-29 17:56     ` Daniel Colascione
2011-12-29 18:18       ` Eli Zaretskii [this message]
2011-12-29 18:53         ` Juanma Barranquero
2011-12-29 14:03 ` [PATCH 2/4] Refactor window-system configuration Daniel Colascione
2011-12-29 22:21   ` Dan Nicolaescu
2011-12-29 22:29     ` Daniel Colascione
2011-12-29 22:43       ` Dan Nicolaescu
2011-12-29 22:48         ` Daniel Colascione
2011-12-29 23:05           ` Dan Nicolaescu
2011-12-29 23:08             ` Daniel Colascione
2011-12-30  8:54             ` Eli Zaretskii
2011-12-30  9:07               ` Daniel Colascione
2011-12-30  9:44                 ` Eli Zaretskii
2011-12-30  0:53       ` Stefan Monnier
2011-12-30  8:21       ` Eli Zaretskii
2011-12-30  8:26         ` Daniel Colascione
2011-12-30  9:38           ` Eli Zaretskii
2011-12-30  9:45             ` Daniel Colascione
2011-12-30 11:15             ` Stefan Monnier
2011-12-30  8:19     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ehvnutpo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.