From: Juanma Barranquero <lektu@terra.es>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Lowercase text after full stop on describe-variable
Date: Thu, 27 Jun 2002 18:27:14 +0200 [thread overview]
Message-ID: <20020627174057.35D7.LEKTU@terra.es> (raw)
In-Reply-To: <200206271424.g5REO1p16162@rum.cs.yale.edu>
On Thu, 27 Jun 2002 10:24:01 -0400, "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> wrote:
> Why not change the describe-* functions to also use a semi-colon ?
Because I'm deeply idiot, that's why. :(
I've followed your suggestion, which really simplifies things.
I've had to normalize a few obsolescence declarations, and in two or
three cases I've taken the liberty of removing redundant obsolescence
info from docstrings when the same or equivalent info is already in the
`make-obsolete*' declaration; now that the info is also shown it makes
no sense to say the same thing twice in a row.
Anyway, I'd be grateful if a native English- or Emacs- speaker checks
the changes I've done :)
I haven't touched the docstring of `font-lock-defaults-alist' because I
find it confusing:
> font-lock-defaults-alist's value is shown below.
>
> Documentation:
> This variable is obsolete;
> use `font-lock-defaults' instead.
> Alist of fall-back Font Lock defaults for major modes.
>
> This variable should not be used any more.
> Set the buffer-local `font-lock-keywords' in the major mode instead.
> [...]
The `make-obsolete-variable' declaration says to use `font-lock-defaults',
and the docstring says to use `font-lock-keywords'. Perhaps the
docstring should be reworked somehow (and the bit about "should not be
used anymore" removed, I suppose).
Only vaguely related: with the recent font-lock hoopla `Info-fontify'
has been deleted. Wouldn't have been more logical to
`make-obsolete-variable' it?
/L/e/k/t/u
next prev parent reply other threads:[~2002-06-27 16:27 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
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 [this message]
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=20020627174057.35D7.LEKTU@terra.es \
--to=lektu@terra.es \
--cc=emacs-devel@gnu.org \
--cc=rms@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.