From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 23009@debbugs.gnu.org
Subject: bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates
Date: Mon, 14 Mar 2016 18:43:03 +0200 [thread overview]
Message-ID: <83y49lc8o8.fsf@gnu.org> (raw)
In-Reply-To: <wvr460wp43qu.fsf@phst2.muc.corp.google.com> (message from Philipp Stephani on Mon, 14 Mar 2016 13:56:41 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Mon, 14 Mar 2016 13:56:41 +0100
>
> I'd suggest the following (and will happily provide patches if
> accepted):
>
> - Don't enable UTF-8 coordinates at all. It is too hard to figure out
> whether they are enabled. Rather, err on the safe side and only use
> single-byte coordinates. (The superior SGR mode, which doesn't suffer
> from this problem, should remain enabled.)
How about providing a user option, off by default, to enable that? A
user who knows that this works on her machine will then be able to use
the feature.
> - In `xterm-mouse--read-number-from-terminal', specify a very short
> timeout. The terminal will always write the entire escape sequence as
> a unit, so waiting only increases the chance to accidentially read
> unrelated events.
Won't this break when working on a remote machine via a slow link?
> - As an optimization, provide a `read-byte' function written in C that
> reads a single byte without taking the current terminal encoding into
> account.
You should be able to achieve the same effect by binding
keyboard-coding-system to no-conversion, no?
next prev parent reply other threads:[~2016-03-14 16:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 12:56 bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates Philipp Stephani
2016-03-14 16:43 ` Eli Zaretskii [this message]
2016-03-14 17:24 ` Philipp Stephani
2016-03-14 23:03 ` Philipp Stephani
2016-03-15 17:57 ` Eli Zaretskii
2016-03-19 17:15 ` Philipp Stephani
2016-03-19 17:16 ` Philipp Stephani
2016-03-25 10:18 ` Eli Zaretskii
2016-03-26 17:31 ` Philipp Stephani
2016-03-26 18:07 ` Eli Zaretskii
2016-03-26 22:26 ` Philipp Stephani
2016-03-27 15:21 ` Eli Zaretskii
2016-04-02 9:43 ` Eli Zaretskii
2016-04-02 19:10 ` Philipp Stephani
2016-04-02 19:53 ` Eli Zaretskii
2016-04-08 8:24 ` Eli Zaretskii
2016-04-16 9:57 ` 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
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=83y49lc8o8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23009@debbugs.gnu.org \
--cc=p.stephani2@gmail.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.
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).