From: Van Ly via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73813@debbugs.gnu.org
Subject: bug#73813: 30.0.91; icomplete-mode keymap unusable in xterm for for/backward completions
Date: Tue, 15 Oct 2024 14:07:00 +0000 [thread overview]
Message-ID: <dcssesxqx2z.fsf@sdf.org> (raw)
In-Reply-To: <861q0hsg9k.fsf@gnu.org> (message from Eli Zaretskii on Tue, 15 Oct 2024 15:27:19 +0300)
Eli Zaretskii <eliz@gnu.org> writes:
>
> lisp/term/xterm.el claims that C-. and C-, should be supported
> starting from xterm version 216 if the modifyOtherKeys resource is set
> to 1. Did you try that?
>
The local xterm is version 372. Merging the following .Xresources
> XTerm*VT100.modifyOtherKeys: 1
> UXTerm*VT100.modifyOtherKeys: 1
does let emacs receive C-, and C-. for icomplete for/backward completes
to work as expected in the xterm.
> You can bind commands to the keys you like even if by default they
> stay unbound. There's no need to make changes in the default
> keybindings because users can bind keys very easily in their own local
> configurations.
From the user's perspective, I recall using icomplete-mode first but
couldn't make the completion selector move in xterm,
icomplete-vertical-mode worked because C-n and C-p were received by
emacs in the xterm.
Having in the documentation the need for xterm version 216 or later
with setting "XTerm*VT100.modifyOtherKeys: 1" will help.
--
vl
next prev parent reply other threads:[~2024-10-15 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 5:44 bug#73813: 30.0.91; icomplete-mode keymap unusable in xterm for for/backward completions Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-15 12:27 ` Eli Zaretskii
2024-10-15 14:07 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-15 14:47 ` Eli Zaretskii
2024-10-15 16:46 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=dcssesxqx2z.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=73813@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=van.ly@sdf.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).