Please rename trusted-content ... to trusted-code

Please rename trusted-content ... to trusted-code

[Richard Stallman]

[[[ 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.

Please let's rename that symbol now before it gets into a release.

-- 
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)

Re: Please rename trusted-content ... to trusted-code

[Ihor Radchenko]

Richard Stallman <rms@gnu.org> writes:

> 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.

This is not true.
Org mode uses this variable to determine whether Org markup should
be trusted. For example, when generating previews.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Re: Please rename trusted-content ... to trusted-code

[Björn Bidar]

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).

Re: Please rename trusted-content ... to trusted-code

[Stefan Kangas]

Björn Bidar <bjorn.bidar@thaodan.de> writes:

> In particular these kinds of grammar discussions are very weary from my
> point of view.

You are free to ignore such discussions, but we take seriously the issue
of proper use of English and won't stop discussing it when we need to.