From: Augusto Stoffel <arstoffel@gmail.com>
To: Brian Cully <bjc@spork.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: master 4c0c9d23ab 1/2: Rewrite the minibuffer lazy highlight feature
Date: Mon, 11 Apr 2022 08:05:08 +0200 [thread overview]
Message-ID: <877d7wb1ez.fsf@gmail.com> (raw)
In-Reply-To: <87a6csxuof.fsf@ditto.jhoto.spork.org> (Brian Cully's message of "Sun, 10 Apr 2022 21:39:02 -0400")
On Sun, 10 Apr 2022 at 21:39, Brian Cully <bjc@spork.org> wrote:
> Po Lu <luangruo@yahoo.com> writes:
>
>> Juri Linkov <juri@jurta.org> writes:
>>
>>> +This function allows to set up the minibuffer so that lazy
>>> +highlighting of its content is applied in the original window.
>>
>> I used to be guilty of this mistake as well, but yesterday I read an
>> style guide according to which "allows to" is not correct English.
Sorry, I was also aware of this; as far as grammar rules go, it is a
pretty logical one. I guess just let it slip out.
I can always create a patch, but it's probably easier for everybody if
someone with commit rights just edit this directly?
> It has always struck my (native speaker) ears as odd, but this
> construction seems to be gaining prominence within the US.
>
>> It's probably prudent to replace that with "allows you to" or "allows
>> users to".
>
> One may also say “allows setting up the minibuffer”, which I
> find the most natural. But any of these choices would be acceptable over
> “allows to”, IMHO.
I slightly prefer "allows doing something". It seems quite normal in
English to use "you" to refer to a generic person (as in "apples are
good for you"), but this is kinda funny if think about it.
> -bjc
next prev parent reply other threads:[~2022-04-11 6:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164961948912.5547.6176778706291368339@vcs2.savannah.gnu.org>
[not found] ` <20220410193810.B2511C00890@vcs2.savannah.gnu.org>
2022-04-11 1:20 ` master 4c0c9d23ab 1/2: Rewrite the minibuffer lazy highlight feature Po Lu
2022-04-11 1:39 ` Brian Cully
2022-04-11 6:05 ` Augusto Stoffel [this message]
2022-04-11 16:49 ` Juri Linkov
2022-04-11 17:14 ` [External] : " Drew Adams
2022-04-12 3:21 ` Richard Stallman
2022-04-12 19:53 ` Drew Adams
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=877d7wb1ez.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=bjc@spork.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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 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.