unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 64088@debbugs.gnu.org
Subject: bug#64088: [PATCH] Make project-root for vc projects return an absolute path
Date: Sat, 12 Aug 2023 03:45:26 +0300	[thread overview]
Message-ID: <16c053e0-cd4b-295d-2dae-e97bcf25f3b3@gutov.dev> (raw)
In-Reply-To: <ierwmz7gwkq.fsf@janestreet.com>

On 11/07/2023 02:45, Spencer Baugh wrote:
> Dmitry Gutov <dmitry@gutov.dev> writes:
>> On 27/06/2023 23:01, Spencer Baugh wrote:
>>> OK, how about this?
>>
>> Maybe we should go in the other direction? And call
>> abbreviate-file-name on them?
>>
>> Because otherwise in project-prompt-project-dir we'll always show the
>> expanded directory names, taking up extra space and usually repeating
>> the full name of the user's home directory for no good reason.
> 
> That seems reasonable if we let-bind directory-abbrev-alist to nil
> around it; otherwise we'll be dependent on the user's configuration and
> we might add a directory in one way, and then they add a new value to
> directory-abbrev-alist and we add it again a second way.

That's also fair.

> Although maybe that's fine?  And probably users of
> directory-abbrev-alist would like to have those abbreviations show up in
> project-prompt-project-dir.

They probably would. But indeed if the list was saved with one 
configuration, and read with another, it could lead to a mistake.

> Also we could always call abbreviate-file-name at
> project-prompt-project-dir time.

Meaning it will be called N times (for the number of projects) every 
time the list is displayed, instead of just once, when the project is 
saved/visited. But maybe it's fine too? How slow could that be?

It's probably not too significant problem either way, no matter which 
direction we choose. And we could revert later.

What do you think? Feel free to submit a new patch (note that the one 
you submitted previously would need the abbreviate-file-name calls added 
to it, before the list is displayed).





  reply	other threads:[~2023-08-12  0:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 20:48 bug#64088: [PATCH] Make project-root for vc projects return an absolute path Spencer Baugh
2023-06-16  5:52 ` Eli Zaretskii
2023-06-17  2:43   ` Dmitry Gutov
2023-06-17  6:25     ` Eli Zaretskii
2023-06-18  0:43       ` Dmitry Gutov
2023-06-17  2:47 ` Dmitry Gutov
2023-06-27 20:01   ` Spencer Baugh
2023-07-10  2:17     ` Dmitry Gutov
2023-07-10 23:45       ` Spencer Baugh
2023-08-12  0:45         ` Dmitry Gutov [this message]
2023-08-19 12:31           ` sbaugh
2023-08-19 12:57             ` sbaugh
2023-08-23  0:24               ` 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=16c053e0-cd4b-295d-2dae-e97bcf25f3b3@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=64088@debbugs.gnu.org \
    --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).