unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org, bjc@spork.org,
	arstoffel@gmail.com, juri@linkov.net
Subject: Re: [External] : Re: master 4c0c9d23ab 1/2: Rewrite the minibuffer lazy highlight feature
Date: Mon, 11 Apr 2022 23:21:14 -0400	[thread overview]
Message-ID: <E1ne75e-0007fF-3m@fencepost.gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488F9B226A087D934DCA363F3EA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Mon, 11 Apr 2022 17:14:51 +0000)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

    > "You can do XYZ."
    > "ABC lets you do XYZ."

There is semantic sloppiness in using "lets" to mean "enables".
Likewise, using "permits" or "allows" is sloppy.  They all refer to
giving permission for or authorizing an action.

For actively making something possible, "enable" is the clear word.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2022-04-12  3:21 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           ` [External] : " Drew Adams
2022-04-12  3:21             ` Richard Stallman [this message]
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=E1ne75e-0007fF-3m@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=bjc@spork.org \
    --cc=drew.adams@oracle.com \
    --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).