bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#66993: [PATCH] project.el: avoid asking user about project-list-file


From: Dmitry Gutov
Subject: bug#66993: [PATCH] project.el: avoid asking user about project-list-file lock
Date: Mon, 20 Nov 2023 04:05:58 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0

On 19/11/2023 17:23, Eli Zaretskii wrote:
Date: Sun, 19 Nov 2023 16:31:22 +0200
Cc:sbaugh@janestreet.com,66993@debbugs.gnu.org
From: Dmitry Gutov<dmitry@gutov.dev>

On 18/11/2023 18:26, Eli Zaretskii wrote:
Even if we decide to do that (and I'm not at all sure we should), how
would that solve the difficulty pointed out by Dmitry?  Even if
savehist is ON by default, the user could turn it OFF, right?
I think the working hypothesis is that they are the same feature: if
project--list is used for saving the previous inputs, it can be covered
by savehist-mode.
Then maybe I'm missing something: savehist is AFAIU a feature that
saves minibuffer history, not just_any_  history.

Perhaps it would be accurate to say that it saves minibuffer histories by default, but it can also save other history variables when 'savehist-additional-variables' is customized.

Are we talking
about minibuffer history here?  I didn't think so.

Let me try to list the similarities and differences.

Similar:

- The contents of project--list come from interactions with the user. They're always a result of the user invoking a command. Sometimes the user will input the project's directory manually in the minibuffer, though in many/most cases that addition will be determined automatically by our code (and yet would still be added to the "project history" in project--list, because that looks like the most helpful approach for this list). - The contents of project--list are, like file-name-history, used during completion when the user is asked to choose the project (when it couldn't be or wouldn't be selected automatically).

Different:

- When writing project--list to disk, we eliminate duplicate entries, both consecutive and distant ones. Again, seems more useful here. - When file-name-history is used, something else is used as the completion table. Whereas project--list *is* the completion table. Whether it should be (in certain order) also used in the input history, is perhaps a potential future improvement.

So I don't know if project--list is a "minibuffer history", but depending on the POV one might decide it's close enough.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]