From: "Ken Manheimer" <ken.manheimer@gmail.com>
To: "David Kastrup" <dak@gnu.org>
Cc: bob@rattlesnake.com, emacs-devel@gnu.org
Subject: Re: NEWS.22: `allows' without an object
Date: Tue, 29 May 2007 12:00:39 -0400 [thread overview]
Message-ID: <2cd46e7f0705290900v32f8d117qe5e49728e5ce524c@mail.gmail.com> (raw)
In-Reply-To: <867iqrx4qd.fsf@lola.quinscape.zz>
On 5/29/07, David Kastrup <dak@gnu.org> wrote:
> "Robert J. Chassell" <bob@rattlesnake.com> writes:
> > You could write, `enables reading mail', too; that makes more sense.
>
> Actually, I find that "enables" is suffering from a similar degree of
> awkwardness. I'd probably use "facilitates reading mail ..." instead:
> this is an enabled-object-free verb, though a bit more pompous. More
> closely related to "allows" would be "permits reading"; this is
> simpler than "facilitates", though, like "allows", slightly wrong as
> this is not a question of permission.
not sure what you mean by "enabled-object-free verb", but i often find
"facilitates" a lot more stuffy than "enables". in any case, they
both avoid misuse of "allows".
> > 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
(i think robert is referring to the point i made, not eli?)
> > humans getting permission from the `movemail' code, as `allow'
> > suggests, but gaining from it the power to act.
exactly. this is one of those subtle misuses which continues because
it is common, yet (i doubt) is part of gradual language evolution,
because relaxing the meaning of "allow" so much would render it
ambiguous.
--
ken
http://myriadicity.net
next prev parent reply other threads:[~2007-05-29 16:00 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
2007-05-29 11:13 ` David Kastrup
2007-05-29 16:00 ` Ken Manheimer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cd46e7f0705290900v32f8d117qe5e49728e5ce524c@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--cc=bob@rattlesnake.com \
--cc=dak@gnu.org \
--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 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.