From: Van Ly via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 73813@debbugs.gnu.org, eliz@gnu.org
Subject: bug#73813: 30.0.91; icomplete-mode keymap unusable in xterm for for/backward completions
Date: Thu, 17 Oct 2024 12:46:36 +0000 [thread overview]
Message-ID: <dcs34kuhp77.fsf@sdf.org> (raw)
In-Reply-To: <87h69brqna.fsf@gmail.com> (message from Robert Pluim on Thu, 17 Oct 2024 12:05:13 +0200)
Robert Pluim <rpluim@gmail.com> writes:
>
> Ah, you want C-n and C-p bound in the minibuffer when using icomplete?
I'd put icomplete-mode and icomplete-vertical-mode in the same category
for binding interop.
> Thatʼs possible, I guess `next-line' and `previous-line' arenʼt that
> useful in that context.
>
> But this is an area with a lot of history regarding the bindings, so
> weʼd need to be careful. Perhaps we should consider '<left>' and
> '<right>' instead, like `icomplete-fido'. Iʼm sure opinions will vary
> :-)
>
One more gotcha. Inside a tmux session on xterm, emacsclient won't see
C-, and C-. and maybe there are setting changes needed there.
--
vl
next prev parent reply other threads:[~2024-10-17 12:46 UTC|newest]
Thread overview: 24+ 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
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
2024-10-16 13:03 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-16 13:58 ` Robert Pluim
2024-10-17 6:30 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-17 7:15 ` Robert Pluim
2024-10-17 9:34 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-17 10:05 ` Robert Pluim
2024-10-17 12:27 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-17 12:46 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-17 13:17 ` Robert Pluim
2024-10-17 15:53 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-18 7:59 ` Robert Pluim
2024-10-18 11:48 ` Robert Pluim
2024-10-18 12:48 ` Eli Zaretskii
2024-10-18 13:50 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-18 11:54 ` Robert Pluim
2024-10-18 12:46 ` João Távora
2024-10-18 13:57 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-16 14:01 ` Eli Zaretskii
2024-10-17 6:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dcs34kuhp77.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=73813@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rpluim@gmail.com \
--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 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.