From: Ergus <spacibba@aol.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: Completions and history
Date: Tue, 12 Apr 2022 18:53:44 +0200 [thread overview]
Message-ID: <20220412165344.he5bxd5poymex2yt@Ergus> (raw)
In-Reply-To: <86v8vetgst.fsf@mail.linkov.net>
On Tue, Apr 12, 2022 at 07:20:02PM +0300, Juri Linkov wrote:
>>>> I suppose that this has been discussed before... so is there a reason
>>>> why this has not been implemented? Should I open a feature request or is
>>>> someone already opened?
>>>
>>> Indeed, this has been discussed recently in
>>> https://lists.gnu.org/archive/html/emacs-devel/2021-12/msg00802.html
>>> but no feature request was opened, since C-TAB is already taken by
>>> file-cache-minibuffer-complete.
>>
>> At least could we have documented how to enable this and then let the
>> user set it? Ivy users will find it comfortable in C-r to substitute the
>> Current isearch-backward, other may prefer something else. The default
>> binding may be agreed latter.
>
>One problem is that completions are sorted alphabetically that
>makes no sense for history items which are sorted chronologically.
>So the first thing to do would be to add sorting keys in Completions
>that will allow switching the order between alphabetical and unsorted
>(history items are in chronological order, so unsorted should keep it)
>that will change the value of 'completions-sort'.
>
I have no idea about that, but it makes sense as you explain it.
>Another question: should duplicate history items be retained
>in the Completions window when history-delete-duplicates is nil?
In principle yes... unless you add another custom for that... But the
first is the important part.. to have the history list in order...
next prev parent reply other threads:[~2022-04-12 16:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220411112901.kv3lsyvx6yxwjbph.ref@Ergus>
2022-04-11 11:29 ` Completions and history Ergus
2022-04-11 16:56 ` Juri Linkov
2022-04-11 17:40 ` Ergus
2022-04-12 16:20 ` Juri Linkov
2022-04-12 16:53 ` Ergus [this message]
2022-04-12 16:59 ` Ergus
2022-04-12 17:12 ` Juri Linkov
2022-04-12 17:35 ` Ergus
2022-04-12 18:10 ` Juri Linkov
2022-04-12 17:24 ` Augusto Stoffel
2022-04-12 17:50 ` [External] : " Drew Adams
2022-04-12 18:05 ` Juri Linkov
2022-04-12 19:49 ` Drew Adams
2022-04-13 7:50 ` Juri Linkov
2022-04-13 12:00 ` Augusto Stoffel
2022-04-13 12:12 ` Po Lu
2022-04-14 2:56 ` Richard Stallman
2022-04-13 16:40 ` Drew Adams
2022-04-13 17:58 ` Juri Linkov
2022-04-13 17:57 ` Juri Linkov
2022-04-13 15:49 ` Drew Adams
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=20220412165344.he5bxd5poymex2yt@Ergus \
--to=spacibba@aol.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 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).