From: Spencer Baugh <sbaugh@janestreet.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 64088@debbugs.gnu.org
Subject: bug#64088: [PATCH] Make project-root for vc projects return an absolute path
Date: Mon, 10 Jul 2023 19:45:25 -0400 [thread overview]
Message-ID: <ierwmz7gwkq.fsf@janestreet.com> (raw)
In-Reply-To: <2690528f-bfc8-d164-c522-cd2fcf2ba1ba@gutov.dev> (Dmitry Gutov's message of "Mon, 10 Jul 2023 05:17:39 +0300")
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.
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.
Also we could always call abbreviate-file-name at
project-prompt-project-dir time.
next prev parent reply other threads:[~2023-07-10 23: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 [this message]
2023-08-12 0:45 ` Dmitry Gutov
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=ierwmz7gwkq.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=64088@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
/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).