From: Juanma Barranquero <lektu@terra.es>
Cc: emacs-devel@gnu.org
Subject: Re: Lowercase text after full stop on describe-variable
Date: Tue, 25 Jun 2002 11:37:26 +0200 [thread overview]
Message-ID: <20020625110923.5931.LEKTU@terra.es> (raw)
In-Reply-To: <200206242020.g5OKKHd04156@rum.cs.yale.edu>
On Mon, 24 Jun 2002 16:20:17 -0400, "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> wrote:
> Not that I can see apart from the fact that caddr is not defined
> unless you (require 'cl). Feel free to install it
Ok, I have a patch using `nth' instead.
WRT the upper/lower-case issue, what should I do with variables or
functions which have a NEW string (as opossed to a NEW function/variable)
starting with lowercase, not ending with a stop, or otherwise
non-normalized? Normalize them?
Currently they are:
- Variables:
inhibit-local-variables
unread-command-char
unread-command-event
before-change-function
after-change-function
post-command-idle-hook
post-command-idle-delay
- Functions:
frame-update-faces (no stop)
char-bytes (no stop)
baud-rate
string-to-sequence (no stop)
`move-to-column-force' (from rect.el) is an exception because its
docstring already says that the function is obsolete, and the
make-obsolete declaration is wrong (it is passing as a NEW a string
instead of a symbol, but the string is just the name of a function).
So, what I propose is:
1.- Installing the patch so describe-function shows the obsolescent
information too like describe-variable does now.
2.- Changing the "not documented" strings from those functions and
`describe-face' to "Not documented".
3.- Normalizing the NEW strings currently passed to `make-obsolete' and
`make-obsolete-variable'.
4.- Remove the obsolescence information from `move-to-column-force's
docstring and fixing its make-obsolete declaration.
It is OK to proceed?
/L/e/k/t/u
next prev parent reply other threads:[~2002-06-25 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 13:49 Lowercase text after full stop on describe-variable Juanma Barranquero
2002-06-24 15:23 ` Stefan Monnier
2002-06-24 16:03 ` Juanma Barranquero
2002-06-24 16:29 ` Juanma Barranquero
2002-06-24 20:20 ` Stefan Monnier
2002-06-25 9:37 ` Juanma Barranquero [this message]
2002-06-25 14:20 ` Stefan Monnier
2002-06-25 17:04 ` Juanma Barranquero
2002-06-25 11:07 ` Richard Stallman
2002-06-27 8:54 ` Juanma Barranquero
2002-06-27 14:24 ` Stefan Monnier
2002-06-27 16:27 ` Juanma Barranquero
2002-06-27 16:44 ` Stefan Monnier
2002-06-27 19:14 ` Colin Walters
2002-06-28 6:41 ` Juanma Barranquero
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020625110923.5931.LEKTU@terra.es \
--to=lektu@terra.es \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.