9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tristan Seligmann <mithrandi@mithrandi.za.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] acme: some thoughts about design
Date: Sun, 30 May 2004 01:56:35 +0200	[thread overview]
Message-ID: <20040529235635.GA20444@mithrandi.za.net> (raw)
In-Reply-To: <018b01c445cf$17086730$347e7d50@SOMA>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

On Sun, May 30, 2004 at 00:48:40 +0200, boyd, rounin wrote:
> > really has 1 or 2
> 
> run du -a lately?

The problem is, if I want to associate a file with, say, "computers" and
"vaccuum cleaners", how do I layout my filesystem? (let's say the file
is a write-up about computer-controlled vaccuum cleaners)

> > It may be a great low-level implementation, but being
> > able to say "find the e-mail I wrote to Timothy last week" is a lot more
> > useful to the user.
> 
> really?  mbox/Timothy/* or mbox/Timothy/YYYY/MMDD/*

Ok, now what about "all work-related e-mail I wrote about cars last
month"?

All of these queries can be "displayed" via a hierarchical file view,
but not simultaneously; you could of course build multiple "views" using
symlinks or unions or similar, but that's what I'd consider
"higher-level".

-- 
mithrandi, i Ainil en-Balandor, a faer Ambar

[-- Attachment #2.1: Type: text/plain, Size: 333 bytes --]

from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/pgp-signature; name="signature.asc"
	Content-Description: Digital signature
	Content-Disposition: inline

[-- Attachment #2.2: signature.asc.suspect --]
[-- Type: application/octet-stream, Size: 196 bytes --]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAuSMzpNuXDQIV94oRAniKAJ9JFHoi3LyNeERKi08yEEV5zum5AgCeO3cR
LQwylAh3aXdh8VPYLIWSfPs=
=rUWi
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-05-29 23:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-29 16:51 Tiit Lankots
2004-05-29 16:58 ` Tristan Seligmann
2004-05-29 17:34   ` dvd
2004-05-30  3:49     ` Joel Salomon
2004-05-29 22:48   ` boyd, rounin
2004-05-29 23:56     ` Tristan Seligmann [this message]
2004-05-29 23:54       ` boyd, rounin
2004-05-29 23:59       ` boyd, rounin
2004-05-30  0:51         ` Tristan Seligmann
2004-05-30  3:40           ` Joel Salomon
2004-05-31  9:19           ` a
2004-05-31 10:17             ` Bruce Ellis
2004-05-30 18:09         ` Bruce Ellis
2004-05-29 17:40 ` Matthias Teege
2004-05-29 22:43 ` boyd, rounin
  -- strict thread matches above, loose matches on Subject: below --
2004-05-31  5:46 YAMANASHI Takeshi
2004-05-31 21:03 ` Tristan Seligmann
2004-05-29 17:58 Tiit Lankots
2004-05-29  9:28 Matthias Teege
2004-05-29 14:48 ` Russ Cox
2004-05-29 16:18   ` Matthias Teege
2004-05-29 18:31     ` 9nut

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=20040529235635.GA20444@mithrandi.za.net \
    --to=mithrandi@mithrandi.za.net \
    --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).