From: Alvaro Ramirez <alvaro@xenodium.com>
To: Yuri Khan <yuri.v.khan@gmail.com>, emacs-devel@gnu.org
Subject: Re: Keen on a dired-hide-details-mode patch?
Date: Sun, 21 Jul 2024 21:13:24 +0100 [thread overview]
Message-ID: <m25xsybj17.fsf@xenodium.com> (raw)
In-Reply-To: <CAP_d_8Wwk64jE3wwTzUewoz6YYK7_K0a8TkUQTrOa=kaQBaaUQ@mail.gmail.com> (Yuri Khan's message of "Mon, 22 Jul 2024 02:50:09 +0700")
Yuri Khan <yuri.v.khan@gmail.com> writes:
> On Sun, 21 Jul 2024 at 23:14, Alvaro Ramirez
> <alvaro@xenodium.com> wrote:
>
>> I have rough changes to enable hiding Dired’s absolute path via
>> dired-hide-details-mode.
>>
>> Given a Dired header path like:
>>
>> /long/path/to/some/location/that/goes/deep/into/emacs/lisp/eshell:
>>
>> dired-hide-details-mode would display it as:
>>
>> eshell:
>
> Will that be gated behind a separate setting?
Sure. Can do.
> Because some of the
> projects I work on consist of multiple components with an
> …/include
> and a …/src in each so it’s vital to see the full path.
Curious, in addition to dired header, wouldn't you also have
de-duping details in the buffer name (and thus mode line)? I'm
guessing I'm relying on the uniquify built-in package for this.
>
> (Well, maybe stripping the project root to just its basename
> would be nice.)
next prev parent reply other threads:[~2024-07-21 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 16:07 Keen on a dired-hide-details-mode patch? Alvaro Ramirez
2024-07-21 16:23 ` Eli Zaretskii
[not found] ` <m27cdehavc.fsf@xenodium.com>
2024-07-21 18:38 ` Alvaro Ramirez
2024-07-28 18:00 ` Alvaro Ramirez
2024-07-21 19:50 ` Yuri Khan
2024-07-21 20:13 ` Alvaro Ramirez [this message]
2024-07-21 20:19 ` Yuri Khan
2024-07-31 16:27 ` Alvaro Ramirez
2024-07-31 19:40 ` Charles Choi
2024-08-01 16:31 ` Alvaro Ramirez
2024-08-01 19:39 ` Charles Choi
2024-08-02 10:40 ` Alvaro Ramirez
2024-07-22 11:20 ` Eli Zaretskii
2024-07-22 6:29 ` Charles Choi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m25xsybj17.fsf@xenodium.com \
--to=alvaro@xenodium.com \
--cc=emacs-devel@gnu.org \
--cc=yuri.v.khan@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.