From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, "rms@gnu.org" <rms@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Please rename trusted-content to trusted-contents
Date: Sun, 22 Dec 2024 18:30:50 +0000 [thread overview]
Message-ID: <DS7PR10MB52328458FEC2E495C9D9ECE2F3012@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <jwvh66wba58.fsf-monnier+emacs@gnu.org>
> OK, I tried to figure it out, but at least the info I found wasn't
> very definitive. It seems to have to do with whether it's countable or
> not, or whether it describe the "conceptual ideas" contained as opposed
> to the actual elements contained.
Right. And the distinction isn't very important in
practice, as the two are often used interchangeably
(arguably incorrectly, but ... usage wins in the end,
and who knows what verdict/measure the future will hold).
Googling is helpful. This bit from one search hit
isn't a bad overview:
Thus, while a book has contents (sections, chapters,
subchapters, etc.), the content of a book is the story
it tells.
* This is a brief summary of the contents of the book.
* The title says one thing, but the content of the book
is completely different.
https://www.pristineword.com/noun-content-contents/
"Content" is the meaning that's "contained", abstractly,
in something. Something's "contents" are the actual
things contained in it - the something is regarded only
as a container.
You might (sort of) think of this in terms of type
versus constituent/instance. "Content" looks beyond
the contained individuals to what they have in common,
and thus to what they represent/mean collectively.
* The contents of that directory are image files.
It contains files.
* The content of that directory is images (file type:
image). That's the directory's purpose/meaning o.
next prev parent reply other threads:[~2024-12-22 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 5:23 Please rename trusted-content to trusted-contents Richard Stallman
2024-12-20 7:52 ` Eli Zaretskii
2024-12-20 9:42 ` Stefan Kangas
2024-12-20 12:30 ` Eli Zaretskii
2024-12-22 4:06 ` Stefan Kangas
2024-12-22 4:36 ` Stefan Monnier
2024-12-22 4:48 ` Stefan Monnier
2024-12-22 18:01 ` Morgan Willcock
2024-12-22 18:30 ` Drew Adams [this message]
2024-12-23 0:31 ` [External] : " Björn Bidar
2024-12-23 4:08 ` Richard Stallman
2024-12-23 4:08 ` Richard Stallman
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=DS7PR10MB52328458FEC2E495C9D9ECE2F3012@DS7PR10MB5232.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.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).