From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: kbrown@cornell.edu, emacs-devel@gnu.org
Subject: Re: Defining HAVE_MOUSE on Cygwin
Date: Sun, 07 Oct 2012 21:47:29 +0200 [thread overview]
Message-ID: <834nm65ajy.fsf@gnu.org> (raw)
In-Reply-To: <jwvwqz213cl.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Sun, 07 Oct 2012 15:38:24 -0400
> Cc: kbrown@cornell.edu, emacs-devel@gnu.org
>
> >> > But if that works, my fears notwithstanding, why confine this to
> >> > Cygwin? If we believe that emacs-nox will always run on a
> >> > mouse-capable terminal, let's turn on HAVE_MOUSE in all Posix builds.
> >> Actually, I can't see why we have HAVE_MOUSE at all nowadays.
> > Perhaps someone should try compiling a -nox configuration with
> > HAVE_MOUSE defined and without GPM, and see if it works well on a text
> > terminal on Unix or GNU/Linux (a _real_ text terminal, not xterm).
>
> I'm not claiming it works. I'm claiming that there's no good reason why
> it shouldn't work, so if it doesn't work it's a bug. We should remove
> HAVE_MOUSE and fix any breakage that might ensue (but since Emacs works
> fine under xterm with xterm-mouse-mode disabled, I don't expect too
> much breakage at least under GNU/Linux).
If no one beats me to it, I will try that in a GNU/Linux TTY session
one of these days.
next prev parent reply other threads:[~2012-10-07 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 1:56 Defining HAVE_MOUSE on Cygwin Ken Brown
2012-10-07 6:46 ` Eli Zaretskii
2012-10-07 12:18 ` Ken Brown
2012-10-07 14:16 ` Eli Zaretskii
2012-10-07 14:43 ` Stefan Monnier
2012-10-07 15:22 ` Eli Zaretskii
2012-10-07 19:38 ` Stefan Monnier
2012-10-07 19:47 ` Eli Zaretskii [this message]
2012-11-23 22:46 ` Ken Brown
2012-11-24 15:13 ` Stefan Monnier
2012-11-24 17:22 ` Ken Brown
2012-11-24 20:32 ` Stefan Monnier
2012-10-07 17:33 ` Ken Brown
2012-10-07 19:46 ` 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=834nm65ajy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
--cc=monnier@IRO.UMontreal.CA \
/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.