From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Is OpenUsability something for Emacs?
Date: Mon, 21 Aug 2006 12:30:14 -0400 [thread overview]
Message-ID: <87ejvacaqx.fsf@stupidchicken.com> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMOEKLCKAA.drew.adams@oracle.com> (Drew Adams's message of "Mon, 21 Aug 2006 08:35:05 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> > RS> One can't expect users to know about that command. In order for
> > RS> that to be the solution to the no-mouse problem, something on the
> > RS> screen needs to say how to use it.
> >
> > Usability is about using things, not about learning to use
> > things. Would you like to have every possible Emacs keybinding shown
> > on the screen?
>
> When you start up Emacs, it does display some basic keybindings, and
> tells you how to get help.
>
> Perhaps also let the start-up screen explictly mention `C-h b'? E.g.,
>
> `C-h b' shows you all available key bindings in any buffer.
I don't think `C-h b' is useful for new users; it overwhelms with too
much information. The current startup screen seems sufficient.
next prev parent reply other threads:[~2006-08-21 16:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-19 15:15 Is OpenUsability something for Emacs? Lennart Borgman
2006-08-19 20:26 ` Robert J. Chassell
2006-08-20 4:32 ` Richard Stallman
2006-08-20 8:37 ` Lennart Borgman
2006-08-20 11:24 ` Paul Pogonyshev
2006-08-20 13:45 ` Lennart Borgman
2006-08-21 11:12 ` Richard Stallman
2006-08-21 11:23 ` Mikhail Gusarov
2006-08-21 11:45 ` Lennart Borgman
2006-08-21 14:03 ` Chong Yidong
2006-08-21 15:35 ` Drew Adams
2006-08-21 16:30 ` Chong Yidong [this message]
2006-08-22 7:42 ` Richard Stallman
2006-08-22 7:42 ` Richard Stallman
2006-08-21 11:12 ` Richard Stallman
2006-08-21 11:34 ` Lennart Borgman
2006-08-22 22:22 ` David Hansen
2006-08-23 2:24 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2006-08-21 0:58 Mikiya Matsuzaka
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=87ejvacaqx.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--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).