From: Robert Pluim <rpluim@gmail.com>
To: Van Ly <van.ly@sdf.org>
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 15:17:21 +0200 [thread overview]
Message-ID: <877ca6swbi.fsf@gmail.com> (raw)
In-Reply-To: <dcs34kuhp77.fsf@sdf.org> (Van Ly's message of "Thu, 17 Oct 2024 12:46:36 +0000")
>>>>> On Thu, 17 Oct 2024 12:46:36 +0000, Van Ly <van.ly@sdf.org> said:
Van> Robert Pluim <rpluim@gmail.com> writes:
>>
>> Ah, you want C-n and C-p bound in the minibuffer when using icomplete?
Van> I'd put icomplete-mode and icomplete-vertical-mode in the same category
Van> for binding interop.
So that would be this:
diff --git a/lisp/icomplete.el b/lisp/icomplete.el
index 540ed2b5819..05914b24d2c 100644
--- a/lisp/icomplete.el
+++ b/lisp/icomplete.el
@@ -178,6 +178,8 @@ icomplete-minibuffer-map
:doc "Keymap used by `icomplete-mode' in the minibuffer."
"C-M-i" #'icomplete-force-complete
"C-j" #'icomplete-force-complete-and-exit
+ "C-n" #'icomplete-forward-completions
+ "C-p" #'icomplete-backward-completions
"C-." #'icomplete-forward-completions
"C-," #'icomplete-backward-completions
"<remap> <minibuffer-complete-and-exit>" #'icomplete-ret)
I donʼt use icomplete or fido, so I have no real opinion to offer
here, except that it would be nice to have bindings that work without
having to modify xtermʼs configuration.
>> 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
>> :-)
>>
Van> One more gotcha. Inside a tmux session on xterm, emacsclient won't see
Van> C-, and C-. and maybe there are setting changes needed there.
They work for me when using tmux as-is, but not when I use
TERM=xterm-mono inside tmux
Robert
--
next prev parent reply other threads:[~2024-10-17 13:17 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
2024-10-17 13:17 ` Robert Pluim [this message]
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=877ca6swbi.fsf@gmail.com \
--to=rpluim@gmail.com \
--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 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.