From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Please rename trusted-content ... to trusted-code
Date: Wed, 01 Jan 2025 21:51:03 +0200 [thread overview]
Message-ID: <21053.8145782024$1735761133@news.gmane.org> (raw)
In-Reply-To: <E1tSq45-0007r2-RL@fencepost.gnu.org> (Richard Stallman's message of "Tue, 31 Dec 2024 23:10:37 -0500")
Richard Stallman <rms@gnu.org> writes:
> [[[ 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. ]]]
>
> I proposed renaming `trusted-content' to `trusted-contents', the
> smallest possible change. But that raised a somewhat complex issue.
>
> So how about if we rename it to `trusted-code' instead?
>
> It is clear that what's trusted is _the code in that file_.
> So this name is entirely fitting.
I don't think so it is a vague term the trusted-content ultimately refers
to the code in a file but the variable talks about a lit of directory
and files to quote the manual: "You can customize the variable to be a list of one or more
names of trusted files and directories".
Which mean it does refer to the content of these files.
In particular these kinds of grammar discussions are very weary from my
point of view. I expect that native speakers play to their advantage in
such context and offset that the rest of us who speak English
as a second or third language (especially when you take in to account
that GNU demand's demand American English).
next prev parent reply other threads:[~2025-01-01 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 4:10 Please rename trusted-content ... to trusted-code Richard Stallman
2025-01-01 7:48 ` Ihor Radchenko
2025-01-01 19:51 ` Björn Bidar [this message]
[not found] ` <67759ccb.050a0220.204694.c4d1SMTPIN_ADDED_BROKEN@mx.google.com>
2025-01-02 0:50 ` Stefan Kangas
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='21053.8145782024$1735761133@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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.