From: "André A. Gomes" <andremegafone@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: History completion
Date: Wed, 08 Dec 2021 20:02:04 +0000 [thread overview]
Message-ID: <87bl1qq30j.fsf@gmail.com> (raw)
In-Reply-To: <86mtlbvuq2.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 08 Dec 2021 20:54:40 +0200")
Juri Linkov <juri@linkov.net> writes:
> Wouldn't it be nice to allow completion on previous input
> in the minibuffer.
>
> There are two unbound commands ‘previous-complete-history-element’ and
> ‘next-complete-history-element’ but their completion is limited
> only to the beginnings of history items.
>
> So tried to set the minibuffer completion table to the history list:
>
> #+begin_src emacs-lisp
> (defun minibuffer-setup-history-completions ()
> (unless (or minibuffer-completion-table minibuffer-completion-predicate)
> (setq-local minibuffer-completion-table (symbol-value minibuffer-history-variable))))
> (add-hook 'minibuffer-setup-hook 'minibuffer-setup-history-completions)
> #+end_src
This is extremely valuable!!! I have thought about it myself in the
past. My inspiration, perhaps yours too, came from
`comint-previous-matching-input-from-input' and friends.
> It works nicely with ‘icomplete-mode’ and ‘fido-vertical-mode’
> by automatically displaying completions from the history
> depending on input in the minibuffer. But this also has drawbacks:
> while typing a completely new command that doesn't exist in the history,
> it permanently says at the end of the minibuffer: [No matches]
>
> So instead of this, tried to show history completions only after
> typing a special key. TAB can't be reused because in some minibuffers
> such as ‘M-!’ (shell-command), TAB completes the command/file names.
>
> There is ‘C-tab’ bound to file-cache-minibuffer-complete.
> When file-cache is not used, then ‘C-tab’ could be rebound
> to a command that completes on the minibuffer history:
>
> #+begin_src emacs-lisp
> ;; Adapted from ‘minibuffer-complete’:
> (defun minibuffer-complete-history ()
> (interactive)
> (completion-in-region (minibuffer--completion-prompt-end) (point-max)
> (symbol-value minibuffer-history-variable)
> nil))
> (define-key minibuffer-local-map [C-tab] 'minibuffer-complete-history)
> #+end_src
Hopefully I was able to follow you thoroughly.
I think that such a completion should always be triggered by the user,
and not automatically.
To cycle the history ring with a given prefix string, I suggest C-n/p.
The minibuffer is always a single line after all, or am I missing
something? M-n/p can't be taken, and the same applies to C-M-n/p.
Another suggestion would be to follow comint mode's bindings: C-c M-r/s.
But, unlike comint's case, C-c M-p/n aren't being used so it's also an
option.
--
André A. Gomes
"Free Thought, Free World"
next prev parent reply other threads:[~2021-12-08 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 18:54 History completion Juri Linkov
2021-12-08 20:02 ` André A. Gomes [this message]
2021-12-09 6:05 ` Manuel Uberti
2021-12-09 17:12 ` Juri Linkov
2021-12-09 22:52 ` André A. Gomes
2021-12-08 20:52 ` [External] : " Drew Adams
2021-12-09 8:30 ` Daniel Fleischer
2021-12-09 17:16 ` Juri Linkov
2021-12-09 18:13 ` [External] : " Drew Adams
2021-12-09 7:51 ` Manuel Uberti
2021-12-09 17:18 ` Juri Linkov
2021-12-09 17:40 ` Manuel Uberti
2022-06-09 7:01 ` Juri Linkov
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=87bl1qq30j.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
/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.