From: <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: [9fans] acme design
Date: Thu, 3 Jun 2004 09:58:29 +0200 [thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17D06633D@XMAIL.asuch.cas.cz> (raw)
> I think you lost the most important point of acme, that is acme has
> windows recursively,
sorry for ignorance, but can you hint me some more info on this?
> and all the menus we can see on a plane.
as it is in my proposal, but there is no redundance, and menuitems are all just text written into the scrollable "cmd frame"
> It helps us very much from the deeply nested menues which break
> the promise we don't need to read manual. ☺
just make the frame buig enough(for the moment) or scroll..
++pac.
next reply other threads:[~2004-06-03 7:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 7:58 cej [this message]
2004-06-03 8:54 ` Kenji Okamoto
-- 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 11:21 cej
2004-06-03 14:59 ` a
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-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=ACCF003CBA3D09458207DB0CB86AD17D06633D@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).