From: <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: [9fans] acme: some thoughts about design
Date: Fri, 28 May 2004 11:01:53 +0200 [thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17D066334@XMAIL.asuch.cas.cz> (raw)
Hi, there!
First... I love Acme's design: chording, no-menus, etc... Nothing pops up, or falls at me, etc,etc...
The thing I don't like [very much] is taglines [as a place for commands]:
they waste screen space, show redundant info (same commands all the time)
couldn't we have a *single* command 'window'[==acme's frame, not rio window]
which would behave much like tagline: show current window's tag plus list of predefined/pasted commands
this would save space on screen, and [IMHO] would bemore elegant solution.
Another frame with [sorted] listing of window tags could ease navigation...
would love also to have acme as an optional universal glue for programs,
eg., Edit functions could move outside to [something like a commandline]Sam (enhanced sed) that would
then use Acme's frame to display files...
Just a prick in a wasp's nest, I feel, but I would love
to hear from you, even if [especially if] I missed the point! Don't shoot me.
No need to say that implementation is far, far beyond my skills :-(((
Sincerely yours,
++pac.
next reply other threads:[~2004-05-28 9:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 9:01 cej [this message]
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
2004-05-29 23:10 ` Put (was: [9fans] acme: some thoughts about design) FODEMESI Gergely
2004-05-29 16:51 Re: [9fans] acme: some thoughts about design Tiit Lankots
2004-05-29 16:58 ` Tristan Seligmann
2004-05-29 22:48 ` boyd, rounin
2004-05-29 23:56 ` Tristan Seligmann
2004-05-29 23:59 ` boyd, rounin
2004-05-30 18:09 ` Bruce Ellis
2004-05-31 9:19 a
2004-05-31 10:17 ` Bruce Ellis
2004-06-02 11:22 cej
2004-06-02 12:42 ` a
2004-06-02 12:55 ` a
2004-06-03 7:48 cej
2004-06-03 9:10 ` boyd, rounin
2004-06-03 9:51 ` Matthias Teege
2004-06-03 10:14 ` boyd, rounin
2004-06-03 11:22 ` Matthias Teege
2004-06-03 11:34 ` boyd, rounin
2004-06-04 12:52 cej
2004-06-04 18:21 ` boyd, rounin
2004-06-07 7:18 cej
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=ACCF003CBA3D09458207DB0CB86AD17D066334@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).