From: "Robert J. Chassell" <bob@rattlesnake.com>
To: emacs-devel@gnu.org
Subject: Re: NEWS.22: `allows' without an object
Date: Tue, 29 May 2007 10:33:03 +0000 (UTC) [thread overview]
Message-ID: <m1Hsz0h-0027M2C@rattlesnake.com> (raw)
In-Reply-To: <uirac5o1u.fsf@gnu.org> (message from Eli Zaretskii on Tue, 29 May 2007 06:03:25 +0300)
As Alan Mackenzie <acm@muc.de> says, "allow" needs a direct object,
> This version of `movemail' allows you to read mail from a wide range of
> ^^^
I think "allows reading mail" is also okay, and doesn't require "you".
`Reading' serves (or maybe the object is the whole phrase, `reading
mail' -- I don't know.)
Stefan Monnier <monnier@iro.umontreal.ca> wrote
... in most contexts, "blabla to read mail" and "blabla reading
mail" translate into the exact same thing in French, so I tend to
not know when to use which.
I did not know. That explains a great deal.
As Alan Mackenzie says, this instance needs `the person or thing being
empowered'. On its own, in English, the phrase `to read' fails.
The English is confusing. It may be that you can only comfortably
learn this kind of construction when very young.
You could write, `enables reading mail', too; that makes more sense.
Before Eli Zaretskii made this observation, I had not noticed the
distinction between gaining permission and gaining an ability, but it
is there and important. After all, we are not talking about humans
getting permission from the `movemail' code, as `allow' suggests, but
gaining from it the power to act.
--
Robert J. Chassell GnuPG Key ID: 004B4AC8
bob@rattlesnake.com bob@gnu.org
http://www.rattlesnake.com http://www.teak.cc
next prev parent reply other threads:[~2007-05-29 10:33 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
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 [this message]
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=m1Hsz0h-0027M2C@rattlesnake.com \
--to=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).