9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Tags for files
Date: Wed, 13 Oct 2004 19:25:17 +0200	[thread overview]
Message-ID: <3e8f8aa4f9ce3e3a909dcc1aaa87f694@plan9.escet.urjc.es> (raw)
In-Reply-To: <ee9e417a041013101718cf43a1@mail.gmail.com>

> I'm trying to understand this.  It looks to me like in addition to
> what you've said above, you can write filters that get run every
> time a file is noticed to have been created or changed, so
> that tags can be automatically attached. 

Yes. The thing is that the scan script generates an initial set of 
tags for the files. The tags are actually generated by any /bin/tag/f*
script that is found. This is to save you the work of defining tags
that could be defined by a program. For example, I have used
the muid and permissions from the output of ls -l and the
name of elements in the full path name as the initial set of tags.

This is an example. This entry is for $home/src/9/block.c

/src/9/block.c muid=[nemo] perm=--rw-r--r-- usr nemo src 9 block.c

> Can you give examples of what kind of searches you do?

This would allow me to run "F 9 block" from acme. Other searches I do
are

F planb net slides
F tag sys src
F rwxrwxrwx sys
F os course slides


and the like. So far, I have not defined tags by hand. It seems that
in my case the names in the path suffice. But, for example, I added
the permissions as a tag soon after I started to use the program.





  parent reply	other threads:[~2004-10-13 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 16:24 Fco. J. Ballesteros
2004-10-13 17:17 ` Russ Cox
2004-10-13 17:17   ` boyd, rounin
2004-10-13 17:25   ` Fco. J. Ballesteros [this message]
2004-10-13 17:28     ` Fco. J. Ballesteros
2004-10-14  0:56 ` Kenji Okamoto
2004-10-14  6:47   ` Fco. J. Ballesteros

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=3e8f8aa4f9ce3e3a909dcc1aaa87f694@plan9.escet.urjc.es \
    --to=nemo@lsub.org \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).