From: David Kastrup <dak@gnu.org>
Cc: acm@muc.de, snogglethorpe@gmail.com, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: English usage bug in bytecomp.el
Date: Wed, 09 Mar 2005 10:49:50 +0100 [thread overview]
Message-ID: <x5is41du81.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1D8rd5-00070L-3C@fencepost.gnu.org> (Richard Stallman's message of "Tue, 08 Mar 2005 22:12:59 -0500")
Richard Stallman <rms@gnu.org> writes:
> However, a variant which might be even clearer, and maybe less
> objectionable would be
>
> How about "FOO is an obsolete function (now and since 21.4)".
That sounds weird when encountered in the 21.4 release, so one would
need to edit this _again_ after 21.4 has been released (do a
s/21\.4/22.1/g on this posting so that it makes sense). And actually,
it still contains the same grammatical offender, only masked in
alternatives.
> Or "FOO is an obsolete function (marked obsolete in Emacs 21.4)".
"FOO is an obsolete function and has been obsolete since 21.4."
Uh, same problem as with your initial proposal: sounds weird in 21.4
itself.
How about:
"FOO is an obsolete function in version 21.4 and later."
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-03-09 9:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 20:17 English usage bug in bytecomp.el Alan Mackenzie
2005-03-07 23:09 ` Miles Bader
2005-03-08 8:02 ` Alan Mackenzie
2005-03-08 8:49 ` Nick Roberts
2005-03-08 10:24 ` David Kastrup
2005-03-08 11:45 ` Nick Roberts
2005-03-08 9:57 ` Miles Bader
2005-03-08 10:33 ` David Kastrup
2005-03-08 15:37 ` John S. Yates, Jr.
2005-03-08 16:08 ` Bill Wohler
2005-03-08 17:26 ` Andreas Schwab
2005-03-08 21:10 ` Nick Roberts
2005-03-08 22:15 ` Miles Bader
2005-03-08 22:36 ` Bill Wohler
2005-03-09 16:59 ` Richard Stallman
2005-03-09 3:12 ` Richard Stallman
2005-03-09 9:49 ` David Kastrup [this message]
2005-03-09 10:22 ` Miles Bader
2005-03-08 13:08 ` Stefan Monnier
2005-03-09 3:12 ` 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=x5is41du81.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=snogglethorpe@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).