From: Andreas Schwab <schwab@linux-m68k.org>
To: "Langton\, Asher" <langton2@llnl.gov>
Cc: "6594@debbugs.gnu.org" <6594@debbugs.gnu.org>
Subject: bug#6594: <no subject>
Date: Thu, 28 Jul 2011 08:58:18 +0200 [thread overview]
Message-ID: <m339hqgad1.fsf@hase.home> (raw)
In-Reply-To: <CA55DC59.7B10%langton2@llnl.gov> (Asher Langton's message of "Wed, 27 Jul 2011 15:18:29 -0700")
"Langton, Asher" <langton2@llnl.gov> writes:
> On 7/27/11 1:30 PM, Andreas Schwab wrote:
>>"Langton, Asher" <langton2@llnl.gov> writes:
>>
>>> Running through this in the debugger didn't seem very informative, so I
>>> just put a print statement in xterm-mouse-event that displayed the
>>>values
>>> of type, x, and y. For some arbitrary clicks, here was the output (all
>>>in
>>> pairs; mouse-1 and down-mouse-1, I assume):
>>>
>>> In xterm-mouse-event with 0,130023656,46
>>
>>What does your xterm emit?
>
> I'm not sure what that means.
Whatever characters it emits. See C-h l.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-07-28 6:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 17:09 bug#6594: 23.2; xterm-mouse-mode bug Ilya Tatar
2010-07-14 17:57 ` Jan Djärv
2011-04-24 1:59 ` bug#6594: (no subject) Ilya Tatar
2011-04-25 12:06 ` Jan Djärv
2011-07-25 20:00 ` bug#6594: xterm-mouse-mode bug still appears in 23.3.1 Langton, Asher
2011-07-25 21:44 ` bug#6594: <no subject> Langton, Asher
2011-07-27 20:30 ` Andreas Schwab
2011-07-27 22:18 ` Langton, Asher
2011-07-28 6:58 ` Andreas Schwab [this message]
2011-07-28 16:51 ` Langton, Asher
2011-07-25 22:23 ` Langton, Asher
2011-07-26 3:46 ` bug#6594: 23.2; xterm-mouse-mode bug Langton, Asher
2011-07-26 18:53 ` Asher Langton
2011-07-28 19:00 ` Andreas Schwab
2011-07-28 19:01 ` bug#6594: Auto Reply: bug#6594: closed (Re: bug#6594: 23.2; xterm-mouse-mode bug) ilya.tatar
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=m339hqgad1.fsf@hase.home \
--to=schwab@linux-m68k.org \
--cc=6594@debbugs.gnu.org \
--cc=langton2@llnl.gov \
/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).