9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme design
Date: Thu,  3 Jun 2004 14:48:47 +0100	[thread overview]
Message-ID: <855f2a51294c4e27df6f583286e23e28@vitanuova.com> (raw)
In-Reply-To: <4d30561ec4fd4a26b45150a2416c002a@9srv.net>

i been thinking that one way to make the filenames less obtrusive in
acme would be to allow grouping of windows with a common path prefix.

i quite often find myself working in, say
/n/dump/2004/0529/usr/inferno/appl/cmd/scheduler/...  and that really
doesn't give much space for tag commands.

i could imagine some kind of directory-tagged super-window in acme
that contained other windows.  windows inside it whose names were
prefixed by their super-window's tag would show only a pathname
relative to that directory.  dragging a window outside would show the
whole pathname again.

looking at the acme window i'm writing this email in, this would save
much space, and provide a reasonable way of organising windows too (i
quite often find myself doing a Sort, or typing a full pathname and
right-clicking on it, just to find a particular window).

at least with something like this it would be possible to look at an
acme window and work out where all the files are, something that's not
possible with the env var hack, for instance.



  parent reply	other threads:[~2004-06-03 13:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 12:57 cej
2004-06-02 13:20 ` a
2004-06-02 15:18   ` plan9
2004-06-03 13:48   ` rog [this message]
2004-06-03 14:17     ` lucio
2004-06-03 14:34       ` rog
2004-06-03 15:38         ` kiwane
2004-06-03 15:45           ` rog
2004-06-04  9:19     ` Bengt Kleberg
2004-06-04 10:29       ` Axel Belinfante
2004-06-03  0:54 ` Kenji Okamoto
2004-06-03  0:56   ` Kenji Okamoto
2004-06-03  8:35 ` WLad
2004-06-03  8:40 ` vdharani
2004-06-03  7:58 cej
2004-06-03  8:54 ` Kenji Okamoto
2004-06-03  8:07 cej
2004-06-03  8:52 ` plan9
2004-06-03 13:53 ` rog
2004-06-03 13:55 ` rog
2004-06-05  6:09   ` YAMANASHI Takeshi
2004-06-05 10:07     ` Charles Forsyth
2004-06-05 13:48       ` YAMANASHI Takeshi
2004-06-05 15:50         ` Rob Pike
2004-06-06  2:23           ` YAMANASHI Takeshi
2004-06-06  3:25             ` Rob Pike
2004-06-06  7:24               ` YAMANASHI Takeshi
2004-06-06  8:54               ` vdharani
2004-06-03  8:37 cej
2004-06-03 11:21 cej
2004-06-03 14:59 ` a
2004-06-04  9:12 cej
2004-06-04 11:22 cej
2004-06-07  8:22 cej
2004-06-07 13:43 ` Russ Cox
2004-06-07 13:47 ` boyd, rounin

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=855f2a51294c4e27df6f583286e23e28@vitanuova.com \
    --to=rog@vitanuova.com \
    --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).