From: Philip Kaludercic <philipk@posteo.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 50297@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#50297: 28.0.50; Aggregate project functions for project.el
Date: Wed, 22 Sep 2021 18:06:37 +0000 [thread overview]
Message-ID: <87y27opjrm.fsf@posteo.net> (raw)
In-Reply-To: <87cbdb43-7813-3341-3830-8811423a23b6@yandex.ru> (Dmitry Gutov's message of "Wed, 22 Sep 2021 20:34:09 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 22.09.2021 19:44, Philip Kaludercic wrote:
>> I think it would make sense to have some kind of a way to name projects,
>> either by extracting the information from the VCS or via an
>> alias.
>
> If we add this feature, I think most of the names will be more or less
> equal to project root's base name. So it's not like this will add much
> in the way of variety to the table.
Currently yes. But if we were to store more metadata about a project
(nickname, first access, last access, etc.) maybe it might make more
sense.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-09-22 18:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 12:47 bug#50297: 28.0.50; Aggregate project functions for project.el Philip Kaludercic
2021-09-01 1:07 ` Dmitry Gutov
2021-09-02 13:30 ` Philip Kaludercic
2021-09-02 14:45 ` Philip Kaludercic
2021-09-02 15:56 ` Juri Linkov
2021-09-03 1:02 ` Dmitry Gutov
2021-09-03 0:55 ` Dmitry Gutov
2021-09-22 0:31 ` Dmitry Gutov
2021-09-22 7:15 ` Philip Kaludercic
2021-09-22 12:13 ` Dmitry Gutov
2021-09-22 16:00 ` Juri Linkov
2021-09-22 16:44 ` Philip Kaludercic
2021-09-22 17:34 ` Dmitry Gutov
2021-09-22 18:06 ` Philip Kaludercic [this message]
2021-09-22 18:25 ` Dmitry Gutov
2021-09-22 18:53 ` Philip Kaludercic
2021-09-22 18:55 ` Philip Kaludercic
2021-09-23 2:44 ` Dmitry Gutov
2021-09-23 10:46 ` Philip Kaludercic
2021-09-23 11:56 ` Dmitry Gutov
2021-09-23 12:08 ` Philip Kaludercic
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=87y27opjrm.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=50297@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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).