unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
Subject: Re: CL function's docstrings
Date: Fri, 20 May 2005 01:57:28 +0200	[thread overview]
Message-ID: <f7ccd24b0505191657345e6ac4@mail.gmail.com> (raw)
In-Reply-To: <E1DYepa-0008PT-7G@fencepost.gnu.org>

> However, coherence between functions is one factor in what
> makes any particular argument name better or worse.

Sure, of course. That's why I said "absolute".

Anyway, as I share Kim's (and others') worries about even small
changes during a freeze (other than cosmetic, like docstring fixes,
obsolescence declarations, substituting an aliased function with the
original, etc.), I think the best plan is:

 - Use "\(fn ARG1 ARG2...)" now (so 22.1 at least has good cl docstrings)
 - Use the best method available, once we branch 22.1

That represents doing twice the fixing, but I don't mind, and it'll
get us the best results (assuming I don't screw up the docstrings :)

-- 
                    /L/e/k/t/u

  reply	other threads:[~2005-05-19 23:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 23:52 CL function's docstrings Juanma Barranquero
2005-05-17 21:15 ` Stefan Monnier
2005-05-18 12:13   ` Kim F. Storm
2005-05-18 12:50     ` Juanma Barranquero
2005-05-18 22:45   ` Richard Stallman
2005-05-19 13:04     ` Stefan Monnier
2005-05-18  5:20 ` Richard Stallman
2005-05-18  8:09   ` Juanma Barranquero
2005-05-19  6:48     ` Richard Stallman
2005-05-19 23:57       ` Juanma Barranquero [this message]
2005-05-21  4:47         ` Richard Stallman

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=f7ccd24b0505191657345e6ac4@mail.gmail.com \
    --to=lekktu@gmail.com \
    /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).