unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Simen Heggestøyl" <simenheg@runbox.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
	"Philip K." <philip@warpmail.net>,
	emacs-devel <emacs-devel@gnu.org>, Juri Linkov <juri@linkov.net>
Subject: Re: New feature in project.el: Remembering the previously used projects
Date: Thu, 04 Jun 2020 20:33:58 +0200	[thread overview]
Message-ID: <34549.1046247602$1591295692@news.gmane.org> (raw)
In-Reply-To: <2e54d4da-54ab-50dc-09df-580572d2b5f0@yandex.ru> (Dmitry Gutov's message of "Thu, 4 Jun 2020 02:17:28 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 04.06.2020 01:34, Juri Linkov wrote:
>
>> While using this new feature, I discovered that switching projects
>> by directory is not quite handy, directory strings are too long
>> and begin with the same prefix.
>
> Interesting. It's not really the case here, but I imagine how it is
> possible to be true for many people.

Same. I'm using Ivy for completion though, maybe that plays a role.

>> I think there is a need for an additional command to switch projects by name.
>> A clear advantage of Lisp data is that in this case project names
>> could be saved in the same file ~/.emacs.d/projects, e.g.:
>>    (("/project/path/"
>>      (name . "Project name"))
>> or after implementing the proposal from bug#41572 to use
>> .dir-locals.el,
>> then maybe to save the project name in .dir-locals.el like
>>    ((nil . ((project-name . "Project name")
>
> That's an option, but I wonder if we could do without it:
>
>> A separate question is how to assign a name to a project.
>
> One way to avoid that, is to generate project names on the fly, in a
> uniquify fashion. If base directory names are unique, use those. 
> Otherwise, prepend their parent names, and so on.
>
> And we won't need a separate command.

Generating the names on the fly in a uniquify fashion sounds like good
idea to me (in the beginning this feature feature actually did just
that, but I later changed it to what we have now for simplicity).

> The exact strategy could be a user option, though.

Yep. I imagine different ways the name could be derived from the path
automatically (also supporting name = path like we have now), and maybe
even an option to let users specify the name manually whenever a new
project is encountered.

Juri Linkov <juri@linkov.net> writes:

>> Maybe it should be renamed from "project-list" to simply "projects" too
>> while we're at it, to match similar files, like "places", "bookmarks",
>> and so on?
>
> Indeed, "projects" is much better.  "project-list" looks like that ugly
> directory name "\Program Files" that caused much trouble to people on
> MS-Windows whereas it should have been named just "\Programs".

Done.

-- Simen



  reply	other threads:[~2020-06-04 18:33 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 20:06 New feature in project.el: Remembering the previously used projects Dmitry Gutov
2020-05-28 23:05 ` Basil L. Contovounesios
2020-05-28 23:29   ` Dmitry Gutov
2020-05-29  7:31     ` Philip K.
2020-05-29 13:51       ` Dmitry Gutov
2020-05-29 15:54         ` Simen Heggestøyl
     [not found]         ` <871rn2ivne.fsf@simenheg@gmail.com>
2020-05-30 10:29           ` Philip K.
2020-06-02 17:04             ` Simen Heggestøyl
     [not found]             ` <5ed68784.1c69fb81.61518.35eeSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-03 11:28               ` Basil L. Contovounesios
2020-05-30 12:38           ` Dmitry Gutov
2020-06-02 17:14             ` Simen Heggestøyl
2020-05-30 21:57           ` Juri Linkov
2020-05-30 23:39             ` Dmitry Gutov
2020-06-01 23:01               ` Juri Linkov
2020-06-02 21:34                 ` Dmitry Gutov
2020-06-03 20:13                   ` Dmitry Gutov
2020-06-03 22:40                     ` Juri Linkov
2020-06-03 23:13                       ` Dmitry Gutov
2020-06-04 21:55                         ` Juri Linkov
2020-06-04 22:37                           ` Dmitry Gutov
2020-06-05  8:33                           ` Philip K.
2020-06-05  8:42                             ` Simen Heggestøyl
2020-06-05 11:44                             ` Dmitry Gutov
2020-06-05 11:59                               ` Philip K.
2020-06-05 13:59                                 ` Philip K.
2020-06-05 17:20                                   ` Dmitry Gutov
2020-06-06  1:24                                   ` Jamie Beardslee
2020-12-19 22:18                                     ` Dmitry Gutov
2020-06-06 23:46                             ` Juri Linkov
2020-06-07  0:40                               ` Dmitry Gutov
2020-06-07 22:38                                 ` Juri Linkov
2020-06-02 17:43             ` Simen Heggestøyl
     [not found]             ` <87a71l2wjf.fsf@simenheg@gmail.com>
2020-06-02 17:57               ` Dmitry Gutov
2020-06-03 22:34               ` Juri Linkov
2020-06-03 23:17                 ` Dmitry Gutov
2020-06-04 18:33                   ` Simen Heggestøyl [this message]
2020-06-04 21:58                   ` Juri Linkov
     [not found]             ` <5ed68fe1.1c69fb81.45e50.0c7cSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-03 11:28               ` Basil L. Contovounesios
2020-05-31 13:00           ` Dmitry Gutov
2020-06-02 17:51             ` Simen Heggestøyl
     [not found]             ` <87k10picej.fsf@simenheg@gmail.com>
2020-06-02 21:33               ` Dmitry Gutov
     [not found]         ` <5ed13064.1c69fb81.4bf5e.dc8eSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-03 11:28           ` Basil L. Contovounesios
2020-06-03 11:27     ` Basil L. Contovounesios
2020-06-03 11:47       ` Dmitry Gutov
2020-06-03 13:38         ` Basil L. Contovounesios
2020-06-03 19:15           ` Simen Heggestøyl
     [not found]           ` <87lfl4x8p0.fsf@simenheg@gmail.com>
2020-06-03 20:11             ` Dmitry Gutov
2020-06-04 18:19               ` Simen Heggestøyl
2020-05-29 22:55 ` Kévin Le Gouguec
2020-05-29 23:22   ` Dmitry Gutov
2020-05-29 23:31     ` Dmitry Gutov
2020-05-30  0:42     ` Dmitry Gutov
2020-05-30  6:05       ` Simen Heggestøyl
     [not found]       ` <5ed1f7ae.1c69fb81.9b99b.4ce7SMTPIN_ADDED_BROKEN@mx.google.com>
2020-05-30 12:42         ` Kévin Le Gouguec
2020-05-30 13:17           ` Dmitry Gutov
2020-05-30 17:05             ` Dmitry Gutov
2020-05-30 18:29               ` Kévin Le Gouguec
2020-06-02 17:29           ` Simen Heggestøyl
     [not found]       ` <877dwuc5zu.fsf@simenheg@gmail.com>
2020-05-30 13:21         ` Dmitry Gutov

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='34549.1046247602$1591295692@news.gmane.org' \
    --to=simenheg@runbox.com \
    --cc=contovob@tcd.ie \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=philip@warpmail.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).