unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dan Hitt <dan.hitt@gmail.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: Help Gnu Emacs Mailing List <help-gnu-emacs@gnu.org>
Subject: Re: file metadata
Date: Sat, 12 Oct 2024 00:16:25 -0700	[thread overview]
Message-ID: <CAOphizJHuUQ_bg9YcctZrorQpy_kiOHAPWoy_U-36BCEjfbi3g@mail.gmail.com> (raw)
In-Reply-To: <87bjzqp9dv.fsf@librehacker.com>

That's a really good question.

You didn't mention your underlying OS or filesystem, although i guess we'd
want emacs to work with whatever metadata system is present.

Do you already have some extra metadata assigned (say with an attribute
called 'description') through (e.g.) ext4?

dan

On Fri, Oct 11, 2024 at 3:23 PM Christopher Howard <
christopher@librehacker.com> wrote:

> Hi, I have a bunch of files in various project that have non-descriptive
> names, but I don't want to change the file names, nor the file contents. It
> would be nice if there was some way I could display my own description of
> the file next to the the file listing, say in dired. Do we have any kind of
> extension, ideally with dired integration, that provides some of kind of
> file metadata system, or interacts with a third party metadata system?
>
> --
> 📛 Christopher Howard
> 🚀 gemini://gem.librehacker.com
> 🌐 http://gem.librehacker.com
>
> בראשית ברא אלהים את השמים ואת הארץ
>
>


  parent reply	other threads:[~2024-10-12  7:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 22:22 file metadata Christopher Howard
2024-10-12  0:58 ` [External] : " Drew Adams
2024-10-12  7:16 ` Dan Hitt [this message]
2024-10-14 14:47   ` Christopher Howard
2024-10-13 22:54 ` Jean Louis
2024-10-14 22:15 ` James Thomas
2024-10-15 22:48   ` James Thomas
2024-10-15 23:32     ` James Thomas
2024-10-15 23:36       ` James Thomas
     [not found] <mailman.80.1728955562.19238.help-gnu-emacs@gnu.org>
2024-10-15 11:16 ` gfp
2024-10-15 20:20   ` Jean Louis

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=CAOphizJHuUQ_bg9YcctZrorQpy_kiOHAPWoy_U-36BCEjfbi3g@mail.gmail.com \
    --to=dan.hitt@gmail.com \
    --cc=christopher@librehacker.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).