public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Thomas Dickey <dickey@his.com>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: xterm and 7-bit control codes
Date: Fri, 13 Aug 2010 07:13:00 -0000 [thread overview]
Message-ID: <20100812163131.V73121@mail101.his.com> (raw)
In-Reply-To: <4C640A08.3090907@ece.cmu.edu>
On Thu, 12 Aug 2010, Ryan Johnson wrote:
> Hi all,
>
> I'm running into a strange one...
>
> At some point in the past (on linux because I didn't know about cygwin yet),
> xterm used to send the following control sequence for a mouse click at row 1,
> col 250
>
> ESC [ M SPC \303\206 ! ESC [ M # \303\206 !
>
> From what I could piece together, the formula for the x position was:
>
> \40+x (x < 96)
> \300+X/64 \200+X%64 (otherwise)
>
> In other words, the first 96 characters were encoded as single octets, with
> all later ones encoded as an octet pair.
As far as I know, xterm's never sent more than one byte for either x/y in
a button event. Ditto for rxvt. It sounds like a useful idea, except
that it would of course be incompatible with the existing applications.
So it would have to be enabled by a new control sequence.
(On the other hand, whatever application you were using at the time may
have translated the characters in that manner).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2010-08-12 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 14:50 Ryan Johnson
2010-08-13 7:13 ` Thomas Dickey [this message]
2010-08-13 22:48 ` Ryan Johnson
2010-08-14 11:57 ` Thomas Dickey
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=20100812163131.V73121@mail101.his.com \
--to=dickey@his.com \
--cc=cygwin-xfree@cygwin.com \
/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.
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).