9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] acme design
Date: Fri,  4 Jun 2004 12:29:45 +0200	[thread overview]
Message-ID: <200406041029.i54ATkV03287@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 04 Jun 2004 09:19:19 +0000." <c9pcgl$ksf$1@newstree.wise.edt.ericsson.se>

Bengt wrote:
> rog@vitanuova.com wrote:
> > 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.

It would be great to have a `blessed' (non-hack) solution to make the
filenames less obtrusive. With unix acme the filename is regularly
longer than the width of the tag, meaning one would have to scroll
in the tag even to Put or Un/Redo - this takes away much of the joy
of using acme.
The env var hack makes acme usable for me on unix, and I'm happy to
use it until a better way of dealing with long filenames comes along.

> does acme use existing environment variables, like wily does?

No, but, for the unix acme you can find a patch in the
plan9 ports CVS repository (no idea how hard it would be to
back port it to plan 9).
I slightly patched that for even more comfort, see below.


Axel.


One thing I noticed: the sorting in mkruneenv pays
special attention to the env var names: case and length.
For me, even more important is that I get the env var
for the longest file name, so, if I have

	home=/home/me
	fo=/home/me/fo
	fofoo=/home/me/fo/foo

then when I'm in directory /home/me/fo/foo/bar
I would like to see $fofoo/bar and not
$fo/foo/bar, and certainly not $home/fo/foo/bar .

I cooked up the following patch, just tested to
see if it works, not used long enough to notice
I overlooked something, nor to know whether it
works as comfortable as in wily.

Index: wind.c
===================================================================
RCS file: /cvs/plan9/src/cmd/acme/wind.c,v
retrieving revision 1.4
diff -r1.4 wind.c

[unrelated differences omitted; line numbers may be off]

650,651c648,649
<       Rune *a, *b;
<       int na, nb;
---
>       Rune *a, *b, *af, *bf;
>       int na, nb, fcmp;
655,656c653,659
<       na = runestrchr(a, '=') - a;
<       nb = runestrchr(b, '=') -  b;
---
>       af = runestrchr(a, '=');
>       bf = runestrchr(b, '=');
>       na = af - a;
>       nb = bf -  b;
>       fcmp = runestrcmp(af, bf);
>       if (fcmp != 0)
>               return -fcmp;






  reply	other threads:[~2004-06-04 10:29 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
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 [this message]
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=200406041029.i54ATkV03287@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --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).