From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Augusto Stoffel <arstoffel@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>, Brian Cully <bjc@spork.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: master 4c0c9d23ab 1/2: Rewrite the minibuffer lazy highlight feature
Date: Mon, 11 Apr 2022 17:14:51 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488F9B226A087D934DCA363F3EA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <864k2z1s73.fsf@mail.linkov.net>
> >> “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.
>
> So rephrased now to the suggested wording.
FWIW -
Generally the simplest, easiest to understand,
and most direct language uses active phrases
like these:
"You can do XYZ."
"ABC lets you do XYZ."
In general, you can drop using "enable" and
"allow". They're use is more verbose and
typically less clear. Just use "let".
["Enable" can be useful for talking about a
feature/widget, etc. But then it's about a
person/program etc. enabling something, not
about something enabling a person to do
something.]
next prev parent reply other threads:[~2022-04-11 17:14 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
2022-04-11 16:49 ` Juri Linkov
2022-04-11 17:14 ` Drew Adams [this message]
2022-04-12 3:21 ` [External] : " 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
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=SJ0PR10MB5488F9B226A087D934DCA363F3EA9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=arstoffel@gmail.com \
--cc=bjc@spork.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--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 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).