From: Nick Roberts <nickrob@snap.net.nz>
Cc: snogglethorpe@gmail.com, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: English usage bug in bytecomp.el
Date: Tue, 8 Mar 2005 21:49:15 +1300 [thread overview]
Message-ID: <16941.26379.290951.460068@farnswood.snap.net.nz> (raw)
In-Reply-To: <Pine.LNX.3.96.1050308073303.661A-100000@acm.acm>
> [Discussion of "`foo' is an obsolete function since 21.4;"]
>
> >> . This combination of "is" and "since" is incorrect English usage.
>
> >I think "is ... since" is pretty common usage actually, and certainly
> >makes sense.
>
> <Gnashes teeth>
>
> Yes, it does make sense and it is regrettably common usage, but it is
> WRONG. It is something that a native English speaker would never say.
> In this case, it is just as easy to be correct.
I don't know if it's correct or not but I think it is effective use of
English. I think its important to remember that English may not be the first
language for many Emacs users. "`foo' is an obsolete function since 21.4" is
concise: it tells the user that foo *is* obsolete and then that it became
obsolete in version 21.4. He doesn't have to understand the many forms of past
tense that English can have.
Nick
next prev parent reply other threads:[~2005-03-08 8: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 [this message]
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
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=16941.26379.290951.460068@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--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).