From: Francesco Potorti` <pot@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: send-invisible is not an obvious name
Date: Tue, 22 Oct 2002 09:09:57 +0200 [thread overview]
Message-ID: <E183tAr-0003ZI-00@pot.cnuce.cnr.it> (raw)
In-Reply-To: <buo7kgbm01q.fsf@mcspd15.ucom.lsi.nec.co.jp> (miles@lsi.nec.co.jp)
> > I had to enter my password and since I knew that a command
> > existed to do that I tried to gess its name, to no avail. I had to do a
> > search for `password' in the manual to find it.
>
> I'd say that's what you're supposed to do, and if you could find it by
> searching the manual, then things are working properly. We can't encode
> documentation into all function names!
I was not clear. I had to look in the manual and to a M-s password RET,
which is not the normal way, and found obviously many instances of the
word before finding what I was looking for.
Okay, this may be a shortcoming of the manual, and indexing
send-invisible properly would correct the problem.
What I meant is that it is not reasonable that a user should look in the
manual for such a basic functionality. It should be immediate and
natural.
[about a mneu entry]
> That would be reasonable; however I think `Send input invisibly' (or
> `without echoing') is a pretty good title for this menu entry...
Tha would do. But it makes no sense to a user. It only makes sense to
a programmer. The user only wants to write invisibly when entering a
password, and that is what he is looking for. A programmer knows that
this is only an instance of a wider range of possibilities, but as for
the practical usage, that function is in fact made for passwords, so the
generalization in the name is only theoretical.
prev parent reply other threads:[~2002-10-22 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 9:19 send-invisible is not an obvious name Francesco Potorti`
2002-10-22 5:27 ` Miles Bader
2002-10-22 6:51 ` Francesco Potorti`
2002-10-22 6:59 ` Miles Bader
2002-10-22 7:09 ` Francesco Potorti` [this message]
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=E183tAr-0003ZI-00@pot.cnuce.cnr.it \
--to=pot@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).