From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: none
Date: Tue, 10 Sep 2002 19:25:35 -0400 [thread overview]
Message-ID: <20020910232535.GA12446@gnu.org> (raw)
In-Reply-To: <87wupurlqw.fsf@sachac.linuxboxen.org>
On Tue, Sep 10, 2002 at 09:56:55PM +0800, Sacha Chua wrote:
> Right now I'm studying textmenu and tmm, trying to figure out what
> kind of a menu system I really want. I guess most people don't think
> tmm is broken (it's actually quite nice), but I wonder if it can be
> improved.
I think tmm is `broken' too, because:
(1) It operates differently from other menus so it's bound to confuse
beginners.
(2) Even once I got used to it a bit, I still found it very awkward to use:
(a) Moving between menus and sub-menus (it just replaces the contents of
the `menu buffer') is way too heavy-weight. A typical drop-down menu
implementation allows you to quickly scan through submenus seeing
what's there, while also preserving all the `parent context' for you
to see.
(b) The arrangement of menu items in the buffer seems often hard to read
quickly.
(c) I find the way the user-input (in the minibuffer) works annoying. I
don't really like using completion when choosing from a small set of
displayed items (because doing so requires me to stop and think about
which key to type corresponds to which displayed), I'd rather just
select directly from the list. You can scroll through the list in
the minibuffer using direction keys, but the `disconnected' nature of
it makes this awkward; it would be _much_ better to just manipulate a
cursor in the displayed list directly (you can do this sort of by
switching to the menu-window, but (1) that's an irritating extra step
you have to take, and (2) moving between menu-items once you're there
is still slow and clumsy [e.g., the huge initial comment that has to
be skipped, the double-column arrangement of items]
[I imagine that if you're using emacs-speak, BTW, you might disagree about
some of this]
(3) It's ugly as hell. Bleah.
-Miles
--
Occam's razor split hairs so well, I bought the whole argument!
next prev parent reply other threads:[~2002-09-10 23:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 15:53 Text mode menu wishlist Sacha Chua
2002-09-09 17:27 ` Alex Schroeder
2002-09-10 1:45 ` Sacha Chua
2002-09-10 7:41 ` Thien-Thi Nguyen
2002-09-10 7:48 ` Miles Bader
2002-09-10 8:35 ` (no subject) Thien-Thi Nguyen
2002-09-10 8:47 ` none Miles Bader
2002-09-10 13:56 ` none Sacha Chua
2002-09-10 23:25 ` Miles Bader [this message]
2002-09-30 5:59 ` none Sacha Chua
2002-10-01 6:18 ` none Richard Stallman
2002-09-10 18:15 ` Text mode menu wishlist Alex Schroeder
2002-09-09 23:34 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-11-28 17:01 iso-8859-1 and non-latin-1 chars Dave Love
2002-12-06 16:38 ` Dave Love
2002-12-10 23:47 ` Dave Love
2002-12-13 2:58 ` Kenichi Handa
2002-12-14 18:31 ` Richard Stallman
2002-12-17 11:41 ` None Kenichi Handa
2003-03-07 12:04 None abrahamade
2005-06-04 0:56 (no subject) Luc Teirlinck
2005-06-05 16:49 ` none Kim F. Storm
2016-09-28 12:26 (unknown) Takesi Ayanokoji
2016-09-28 17:05 ` none John Wiegley
2021-07-27 23:54 (unknown) Troy Hinckley
2021-07-30 21:33 ` none Stefan Monnier
2021-07-31 5:09 ` none Troy Hinckley
2021-07-31 16:22 ` none Stefan Monnier
2021-12-20 2:29 (unknown) Davin Pearson
2021-12-20 14:13 ` none Stefan Monnier
2022-07-21 11:36 (unknown) Gregory Heytings
2022-07-21 16:11 ` none Manuel Giraud
2024-03-13 12:48 (unknown) Eli Zaretskii
2024-03-13 13:57 ` none Po Lu
2024-03-13 14:40 ` none Eric Abrahamsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020910232535.GA12446@gnu.org \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).