unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ken Manheimer" <ken.manheimer@gmail.com>
To: emacs-devel@gnu.org, bob@rattlesnake.com
Subject: NEWS.22: `allows' without an object
Date: Mon, 28 May 2007 19:41:35 -0400	[thread overview]
Message-ID: <2cd46e7f0705281641y7b6f738dl265bc5af519b78a0@mail.gmail.com> (raw)
In-Reply-To: <2cd46e7f0705281639m4e06b938sd0fbcc6d710812dc@mail.gmail.com>

On 5/28/07, Robert J. Chassell <bob@rattlesnake.com> wrote:

> In English, as heard by a native,
>
>     *** New user option `help-at-pt-display-when-idle' allows to
>
> in emacs/etc/NEWS.22 sounds wrong.  It would sound better if it were
>
>     *** New user option `help-at-pt-display-when-idle' allows you to
>                                                               ^^^

well, heck, why not use "enables" instead of "allows"?

"to allow" is to not refuse something, to permit it.  "to enable" is
to activate or provide the means to do something.  seems like 80% of
the time that i see "allows" in instructions, "enables" is what was meant.
(the other 20% of the time, the instructions are properly using the
word to endorse valid inputs, or something like that...)

> looked at the outline, but even that was large, over 5000 lines.  You
> may substitute `GNU Emacs' for `you'.)

"may substitute" - again, permission when something else is meant, in
this case, propriety - "you might substitute `GNU Emacs'..."

i don't mean to claim particular grammar chops, this is just a peeve of mine.
--
ken
http://myriadicity.net

  parent reply	other threads:[~2007-05-28 23:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 21:17 NEWS.22: `allows' without an object Robert J. Chassell
     [not found] ` <2cd46e7f0705281639m4e06b938sd0fbcc6d710812dc@mail.gmail.com>
2007-05-28 23:41   ` Ken Manheimer [this message]
2007-05-29  3:03 ` Eli Zaretskii
2007-05-29  8:48   ` Stefan Monnier
2007-05-29  9:51     ` David Reitter
2007-05-29 19:27     ` Eli Zaretskii
2007-05-29 10:33   ` Robert J. Chassell
2007-05-29 11:13     ` David Kastrup
2007-05-29 16:00       ` Ken Manheimer
2007-05-29  4:10 ` Richard Stallman
2007-05-29  8:20 ` Alan Mackenzie

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=2cd46e7f0705281641y7b6f738dl265bc5af519b78a0@mail.gmail.com \
    --to=ken.manheimer@gmail.com \
    --cc=bob@rattlesnake.com \
    --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 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).