unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Juri Linkov <juri@linkov.net>
Cc: 67310@debbugs.gnu.org, Spencer Baugh <sbaugh@janestreet.com>,
	eliz@gnu.org
Subject: bug#67310: [PATCH] Include the project--list as history when prompting for a project
Date: Sun, 10 Dec 2023 22:32:27 +0200	[thread overview]
Message-ID: <780dbb13-c0ca-9082-936b-3c2ab34084dc@gutov.dev> (raw)
In-Reply-To: <861qbujehq.fsf@mail.linkov.net>

On 10/12/2023 19:43, Juri Linkov wrote:
>>> This change broke the order of 'C-x p p M-n M-n ...',
>> Could you remind me which behavior in 'M-n M-n' the aforementioned change
>> relates to? Is this supposed to be like input history as well, or the
>> contents of the completions table in a certain order?
> It's inappropriate to overwrite the history with the recently visited projects.
> Only user input should be added to history variables because it's actually
> the history of user input.  Therefore, the remaining way to access a list
> of recently visited projects is the future history with 'M-n M-n'.

But... we do overwrite it now, manually constructing the value of input 
history from project--list every time.

So it seems like both "past history" and "future history" show the same 
information now. If so, it might make sense to keep only one.

>> I just tried find-file, and the future history is empty there, so I suppose
>> this is something we added particularly for project-find-file.
> Unlike with project--list, we don't keep a list of recently visited files.
> Once we conducted an experiment to add all visited files to the input file history,
> even when a file was visited without reading a file name in the minibuffer,
> e.g. by typing RET in Dired.  But no one liked this behavior.

I don't remember that experiment, but the description sounds like 
recentf. Which must have its audience (and I use it through Ido's 
"virtual buffers").

Thought the way of accessing that history (only through iteration) might 
have felt limiting in that experiment.





  reply	other threads:[~2023-12-10 20:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 19:58 bug#67310: [PATCH] Include the project--list as history when prompting for a project Spencer Baugh
2023-11-21 11:06 ` Dmitry Gutov
2023-11-21 11:14   ` Dmitry Gutov
2023-11-21 15:17     ` Spencer Baugh
2023-11-22  1:40       ` Dmitry Gutov
2023-11-22 16:18         ` Spencer Baugh
2023-11-22 18:44           ` Dmitry Gutov
2023-11-22 23:14             ` Spencer Baugh
2023-11-23  2:55               ` Dmitry Gutov
2023-11-24 15:50                 ` Spencer Baugh
2023-11-25  2:07                   ` Dmitry Gutov
2023-11-25 17:50                   ` Juri Linkov
2023-11-27 17:10                   ` Juri Linkov
2023-12-10  3:04                     ` Dmitry Gutov
2023-12-10 17:43                       ` Juri Linkov
2023-12-10 20:32                         ` Dmitry Gutov [this message]
2023-12-11 17:12                           ` Juri Linkov
2023-12-12  0:21                             ` Dmitry Gutov
2023-12-14  1:02                               ` sbaugh
2023-12-19 17:35                                 ` Juri Linkov
2023-11-23  6:38               ` Eli Zaretskii
2023-11-25  1:54                 ` Dmitry Gutov
2023-11-25  8:42                   ` Eli Zaretskii
2023-11-25 14:05                     ` Dmitry Gutov
2023-11-25 14:10                       ` Eli Zaretskii
2023-11-25 15:06                         ` Dmitry Gutov
2023-11-25 15:57                           ` Eli Zaretskii
2023-11-25 16:35                             ` Dmitry Gutov
2023-11-22  1:42       ` Dmitry Gutov
2023-11-22 16:21         ` Spencer Baugh

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=780dbb13-c0ca-9082-936b-3c2ab34084dc@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=67310@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --cc=sbaugh@janestreet.com \
    /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).