unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: To non-native English writers: expunging the solecism "This allows to do something."
Date: Mon, 25 Jan 2016 15:25:03 +0100	[thread overview]
Message-ID: <87zivteny8.fsf@gmx.net> (raw)
In-Reply-To: <20160125125156.GB4500@acm.fritz.box> (Alan Mackenzie's message of "Mon, 25 Jan 2016 12:51:56 +0000")

On Mon, 25 Jan 2016 12:51:56 +0000 Alan Mackenzie <acm@muc.de> wrote:

> On Sun, Jan 24, 2016 at 11:54:04PM +0100, Stephen Berman wrote:
>
>> You missed some instances, which I found by running rgrep on the Emacs
>> source tree with this regexp (without the quotes):
>
>> "[^-]\(allow\|enable\|permit\|prevent\|require\)[^-de ]* to "
>
> Yes, I'd overlooked "require"; but there are instances of "requires to"
> which are OK.  The regexp I ended up using was:
>
>     '\b\(require\|allow\|prevent\|permit\|enable\)s\? to\b'

Ah, this is better than mine in that it also find cases where the verb
is at bol or "to" at eol; yet ...

> , and some fancy playing around with -A1 and -B1 flags to grep to find
> instances (and there were a few) where the verb is at the end of a line
> and the "to" at the beginning of the next line (modulo comment markers,
> etc.).
>
>> This does, however, also return several false positives, most of them
>> with "require" (one is written as `require' and one or two of the others
>> should probably be quoted like that).  I don't have time in the next few
>> days to commit a fix for these, so if you do, please go ahead.
>
> Well, I've knocked down quite a few more instances.  I can't guarantee
> there're none left, of course, but there aren't many.

... your regexp misses cases of "allowing to", "requiring to", which
there are a handful of (and I didn't try using -A1 and -B1):

./etc/ORG-NEWS:1602:     =org-attach-method= now supports a new method =lns=, allowing to
./lisp/ruler-mode.el:122:Also allowing to visually change `tab-stop-list' setting using
./lisp/org/ox.el:3470:;; `org-export-with-backend' is a function allowing to locally use
./lisp/org/ChangeLog.1:10415:	(org-element--current-element): Fix bug requiring to parse a quote
./lisp/org/ChangeLog.1:14844:	Check `org-protected' property before allowing to match a footnote.
./lisp/org/ChangeLog.1:17233:	(org-re-property): New function allowing to build a regexp to
./doc/lispref/text.texi:1376:allowing to undo them as a group.  By default, commands
./doc/lispref/markers.texi:343:Most functions that create markers, without an argument allowing to
./doc/emacs/frames.texi:1013:with the mouse, thus allowing to easily resize adjacent windows.

I think that's it (don't worry, I won't try looking for more ;-).

Steve Berman



  parent reply	other threads:[~2016-01-25 14:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 21:06 To non-native English writers: expunging the solecism "This allows to do something." Alan Mackenzie
2016-01-24 22:20 ` Marcin Borkowski
2016-01-24 22:54 ` Stephen Berman
2016-01-25 12:51   ` Alan Mackenzie
2016-01-25 14:03     ` Phillip Lord
2016-01-25 14:25     ` Stephen Berman [this message]
2016-01-25 15:35   ` Richard Stallman
2016-01-25 20:10     ` Stephen Berman
2016-01-25  2:41 ` Drew Adams
2016-01-25 15:13 ` Rostislav Svoboda
2016-01-25 15:16   ` Rostislav Svoboda
2016-01-25 16:18   ` Alan Mackenzie
2016-01-25 19:47     ` Michael Albinus
2016-01-25 16:41   ` Paul Eggert
2016-01-26  9:37     ` Richard Stallman
2016-01-25 15:35 ` Richard Stallman
2016-01-25 16:55   ` Rostislav Svoboda
2016-01-26  5:27     ` Yuri Khan
2016-01-26  9:37     ` Richard Stallman
2016-01-26 10:55       ` Rostislav Svoboda
2016-01-27  0:46         ` Richard Stallman
2016-01-25 23:14   ` Mathieu Lirzin
2016-01-26  3:07     ` Xue Fuqiao
2016-01-27  0:48     ` Richard Stallman
2016-01-27 11:06     ` Alan Mackenzie
2016-01-27 16:31       ` Mathieu Lirzin

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=87zivteny8.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=acm@muc.de \
    --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).