unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Theodor Thornhill via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 47287@debbugs.gnu.org
Subject: bug#47287: 28.0.50; [PATCH] Add command project-remove-known-project
Date: Sun, 21 Mar 2021 07:33:28 +0100	[thread overview]
Message-ID: <06BAC477-828A-42E7-951F-ADD88E931354@thornhill.no> (raw)
In-Reply-To: <fab77a5a-5fb2-d7f4-ec08-0afd6d6a2d5a@yandex.ru>


>> This patch adds an interactive command 'project-remove-known-project',
>> that lets the user interactively remove a project from the project
>> list.  My usecase is that sometimes when a directory is moved, the
>> project isn't deleted from the list.
> 
> What if we added an "inventorization" step in project--ensure-read-project-list? After having the list read, it could remove entries that do not exist anymore (and, if the list has been modified in this procedure, call project--write-project-list).
> 
> This should take care of moved directories, at least once per Emacs session.
> 

Yeah, we could! However, there is one more use case: at work we have lot of repos, some I touch every day, some once in a blue moon. I do not want them cluttering the project-list, so I would rather delete them, and have them  automatically appear for periods where I actually use them. Same with other FOSS projects I only ocasionally contribute to. These are directories I usually dont delete from my drive. 


>> This command is modelled after the already present
>> 'project--remove-from-project-list', but that function isn't
>> interactive, and also has a specific purpose.
> 
> I don't know about a binding, but certainly it's not for project-switch-commands.

Agreed :)

—
Theo




  reply	other threads:[~2021-03-21  6:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20 23:28 bug#47287: 28.0.50; [PATCH] Add command project-remove-known-project Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21  0:27 ` Dmitry Gutov
2021-03-21  6:33   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-21 11:42     ` Dmitry Gutov
2021-03-21  6:17 ` Eli Zaretskii
2021-03-21  6:38   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 12:12     ` Dmitry Gutov
2021-03-21 12:15       ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 23:21       ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-21 23:54         ` Dmitry Gutov
2021-03-22  7:48           ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-22 11:52             ` Dmitry Gutov
2021-03-22 12:29               ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-23 11:37             ` Eli Zaretskii
2021-03-23 12:30               ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-23 12:43                 ` Eli Zaretskii
2021-03-23 12:50                   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-24 23:17                     ` Dmitry Gutov
2021-03-25  0:03                       ` Basil L. Contovounesios
2021-03-25  1:04                         ` Dmitry Gutov
2021-03-25  6:15                           ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-25  7:29                             ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-21 13:24                               ` Dmitry Gutov
2021-09-21 18:36                                 ` Theodor Thornhill 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

  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=06BAC477-828A-42E7-951F-ADD88E931354@thornhill.no \
    --to=bug-gnu-emacs@gnu.org \
    --cc=47287@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=theo@thornhill.no \
    /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).