From: Bill Wohler <wohler@newt.com>
Subject: Re: Tag based dired?
Date: Fri, 23 Jun 2006 16:48:12 -0700 [thread overview]
Message-ID: <87u06bigcj.fsf@olgas.newt.com> (raw)
In-Reply-To: m23bdvft71.fsf@sl392.st-edmunds.cam.ac.uk
Leon <sdl.web@gmail.com> writes:
> Could you give an example of using tag?
I'll guess.
Take mh-e.el for example. Right now, for me, it is in one specific
place on my hard drive, namely, /usr/local/src/emacs/lisp/mh-e/mh-e.el.
I could tag this file with "mail", "emacs", "lisp", "source", "MH-E".
In addition, the lisp files already have a Keywords pseudo-header
field which could be used to automatically tag the files as well.
I could then find this file by specifying any of those tags. I could
limit the number of files I see by specifying more tags.
If you were to use a normal file system, you'd create a directory for
each tag in the system, and create hard links between the directories
for files that share tags.
The major advantage of this system is that it would be easier to
classify and find stuff since you wouldn't have to create--and
remember--a possible arcane path to a file. The disadvantage with this
implementation is that the directories would be huge and unwieldy.
An Emacs interface to this would make it easy to enter tags and to
limit the output to files tagged with those tags.
In the meantime, you might look at locate and locate-with-filter. Why
these functions don't put their output in a dired buffer is beyond me.
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
next prev parent reply other threads:[~2006-06-23 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 0:33 Tag based dired? Xiao-Yong Jin
2006-06-23 21:38 ` Leon
2006-06-23 23:48 ` Bill Wohler [this message]
[not found] ` <mailman.3279.1151106523.9609.help-gnu-emacs@gnu.org>
2006-06-24 3:20 ` Xiao-Yong Jin
2006-06-24 19:09 ` Leon
2006-06-26 8:58 ` Mathias Dahl
2006-06-26 12:16 ` Xiao-Yong Jin
2006-06-27 8:36 ` Mathias Dahl
2006-06-27 0:59 ` Bill Wohler
2006-06-27 14:58 ` Mathias Dahl
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=87u06bigcj.fsf@olgas.newt.com \
--to=wohler@newt.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.