9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: [9fans] acme design
Date: Thu,  3 Jun 2004 13:21:00 +0200	[thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17D2012B8@XMAIL.asuch.cas.cz> (raw)


> - how will one know what is the filename (pathname) for each window?
> - in acme, just by looking into the tag line, i know i can run 'grep XXXXX
> *.c' on a particular window. how can i do it with this?

if Acme remembers, which "normal frame" has been touched the last, [and it does, doesn't it?]
then it applies to it

> - the (new) windows on the right are the ones used for tags and commands.
> now, how much space would they occupy? 
as much as you wish, of course, as normal ones...

> what happens when the pathnames and
> commands are longer than the ones in the sample image?

nothing, text wraps as in normal text frame...

> - you have safely assumed there will be only one column (of windows). what
> happens when you have to have 2 or even 3 columns? even in 1024x768, one
> could manage with 2 columns. with your idea, wont it waste space?

no. have as many cols as you wish [see Newcol] . New frame, like new column,
could appear just at the end, and zou could drag it anywhere.
Perhaps the quick drawing was too simple, sorry for that. And, once more, thanks for the
debate.

++pac.



             reply	other threads:[~2004-06-03 11:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 11:21 cej [this message]
2004-06-03 14:59 ` a
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  8:22 cej
2004-06-07 13:43 ` Russ Cox
2004-06-07 13:47 ` boyd, rounin
2004-06-04 11:22 cej
2004-06-04  9:12 cej
2004-06-03  8:37 cej
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  7:58 cej
2004-06-03  8:54 ` Kenji Okamoto
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
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

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=ACCF003CBA3D09458207DB0CB86AD17D2012B8@XMAIL.asuch.cas.cz \
    --to=cej@gli.cas.cz \
    --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).