From: Burton Samograd <burton@samograd.ca>
To: bug-gnu-emacs@gnu.org
Subject: Re: bug#13112: 24.2.90; The cygw32 build should disable X11
Date: Sat, 08 Dec 2012 11:37:36 -0700 [thread overview]
Message-ID: <874njwxudr.fsf@samograd.ca> (raw)
In-Reply-To: mailman.14838.1354954003.855.bug-gnu-emacs@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Burton Samograd <burton@samograd.ca>
>> Date: Fri, 07 Dec 2012 18:51:59 -0700
>>
>> >>> Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a
>> >>> cygw32 Emacs? They shouldn't, AFAIU.
>> >>
>> >> They are on my build, but I have the proper X11 headers and libraries
>> >> installed in my cygwin. I like it that way so I can display my emacs
>> >> with an x-server.
>> >
>> > But you didn't build Emacs with --with-w32, did you? As much as I'd
>> > like a single Emacs binary to support both X11 and W32, we're a long
>> > way away from there.
>>
>> No, I don't use --with-w32.
>
> Then yours is not the cygw32 build, and I was asking only about that.
>
>> I just wanted to make sure a feature I use didn't get removed from
>> the build :)
>
> How can you seriously think we would consider removing X11 support
> from Emacs?
I thought you were discussing removing X11 support from the windows
builds:
>> >>> Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a
>> >>> cygw32 Emacs? They shouldn't, AFAIU.
I didn't realize that cygw32 meant that you use the --with-w32 options.
Cygw32 was something I had never heard of and I thought it just meant
the regular cygwin builds.
I don't think that use of emacs through X11 on windows is a hugely
common occurance, but I use it so I thought I would use my voice. Just
some confusion about what you were actually talking about, so my
mistake.
--
Burton Samograd
next prev parent reply other threads:[~2012-12-08 18:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 13:04 bug#13112: 24.2.90; The cygw32 build should disable X11 Ken Brown
2012-12-07 14:45 ` Ken Brown
2012-12-07 18:01 ` Glenn Morris
2012-12-07 18:24 ` Achim Gratz
2012-12-07 18:40 ` Glenn Morris
2012-12-07 19:18 ` Achim Gratz
2012-12-07 21:23 ` Eli Zaretskii
2012-12-07 21:45 ` Ken Brown
2012-12-07 21:32 ` Ken Brown
2012-12-08 11:29 ` Achim Gratz
2012-12-08 12:23 ` Ken Brown
2012-12-08 12:42 ` Ken Brown
2012-12-08 13:08 ` Achim Gratz
2012-12-08 15:57 ` Ken Brown
2012-12-08 14:10 ` Achim Gratz
[not found] ` <mailman.14806.1354915487.855.bug-gnu-emacs@gnu.org>
2012-12-07 22:19 ` Burton Samograd
2012-12-07 22:36 ` Daniel Colascione
[not found] ` <mailman.14821.1354919805.855.bug-gnu-emacs@gnu.org>
2012-12-08 1:51 ` Burton Samograd
2012-12-08 8:06 ` Eli Zaretskii
[not found] ` <mailman.14838.1354954003.855.bug-gnu-emacs@gnu.org>
2012-12-08 18:37 ` Burton Samograd [this message]
2012-12-09 0:09 ` Ken Brown
2012-12-11 17:30 ` Achim Gratz
2012-12-11 18:29 ` Ken Brown
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874njwxudr.fsf@samograd.ca \
--to=burton@samograd.ca \
--cc=bug-gnu-emacs@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).