unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: Argument names in Elisp Reference vs docstrings
Date: Sat, 17 Sep 2005 02:48:42 +0300	[thread overview]
Message-ID: <87br2sim51.fsf@jurta.org> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICGEKACMAA.drew.adams@oracle.com> (Drew Adams's message of "Fri, 16 Sep 2005 16:19:38 -0700")

> I didn't realize this was already decided. Are these default values
> accessed via repeated M-n?

Yes, very much like values from the history list are accessed via
repeated M-p.

> Is there any limit (or guideline) on their number?

Do you mean a cardinal or ordinal number?

Their amount is limited by the length of the list of default values.

There are no guidelines for their ordinal number in the minibuffer,
like there are no guidelines for the history list.

> My point was that "init" or "initial" does not by itself indicate an initial
> _value_. There are other things that might be initial in this context.
> "initial" is not clear in the same way that "default" is clear. People don't
> say, "What is the "initial?"

I agree with your reasoning.  But OTOH there are many argument names
which are adjectives like "existing" and "special".  And "initial" is
widely used too.  My goal was not to make such arguments clearer, but
to make argument names of related functions consistent between each other
and between docstrings and manuals.

> All of the following are clearer than "initial": "init-val", "init-value",
> "initial-value".

As there exist already only three different argument names: "initial",
"initial-contents" and "initial-input", I'd choose one of existing names
instead of introducing new names like "init-val" or "initial-value".

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2005-09-16 23:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 14:46 Argument names in Elisp Reference vs docstrings Juanma Barranquero
2005-09-14 14:08 ` Richard M. Stallman
2005-09-15 22:03   ` Juri Linkov
2005-09-16 12:02     ` Andreas Schwab
2005-09-16 22:14       ` Juri Linkov
2005-09-16 12:59     ` Richard M. Stallman
2005-09-16 22:16       ` Juri Linkov
2005-09-17 13:39         ` Richard M. Stallman
2005-09-17 14:30           ` Drew Adams
2005-09-17 20:20             ` Robert J. Chassell
2005-09-19 15:54               ` Drew Adams
2005-09-19 17:15                 ` Robert J. Chassell
2005-09-19  1:31             ` Richard M. Stallman
2005-09-19  8:04               ` Kim F. Storm
2005-09-16 14:59     ` Drew Adams
2005-09-16 15:28       ` Juanma Barranquero
2005-09-16 22:17       ` Juri Linkov
2005-09-16 23:19         ` Drew Adams
2005-09-16 23:48           ` Juri Linkov [this message]
2005-09-17  0:53             ` Drew Adams

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=87br2sim51.fsf@jurta.org \
    --to=juri@jurta.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).