* Please rename trusted-content to trusted-contents @ 2024-12-20 5:23 Richard Stallman 2024-12-20 7:52 ` Eli Zaretskii 0 siblings, 1 reply; 4+ messages in thread From: Richard Stallman @ 2024-12-20 5:23 UTC (permalink / raw) To: emacs-devel [[[ 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. ]]] "Contents" and "content" are two different words, and for this meaning, "contents" is correct. It means the contents of the file, and that's what we refer to here. 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) ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Please rename trusted-content to trusted-contents 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 0 siblings, 1 reply; 4+ messages in thread From: Eli Zaretskii @ 2024-12-20 7:52 UTC (permalink / raw) To: rms; +Cc: emacs-devel > From: Richard Stallman <rms@gnu.org> > Date: Fri, 20 Dec 2024 00:23:32 -0500 > > "Contents" and "content" are two different words, and for this > meaning, "contents" is correct. It means the contents of the > file, and that's what we refer to here. > > Please let's rename that symbol now before it gets into a release. The Emacs 30.0.93 pretest was already uploaded with "trusted-content" in it. So if we rename it now, we will need to support both spellings, via defvaralias. I'm not sure the problem is acute enough to justify such last-minute changes. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Please rename trusted-content to trusted-contents 2024-12-20 7:52 ` Eli Zaretskii @ 2024-12-20 9:42 ` Stefan Kangas 2024-12-20 12:30 ` Eli Zaretskii 0 siblings, 1 reply; 4+ messages in thread From: Stefan Kangas @ 2024-12-20 9:42 UTC (permalink / raw) To: Eli Zaretskii, rms; +Cc: emacs-devel Eli Zaretskii <eliz@gnu.org> writes: >> From: Richard Stallman <rms@gnu.org> >> Date: Fri, 20 Dec 2024 00:23:32 -0500 >> >> "Contents" and "content" are two different words, and for this >> meaning, "contents" is correct. It means the contents of the >> file, and that's what we refer to here. >> >> Please let's rename that symbol now before it gets into a release. > > The Emacs 30.0.93 pretest was already uploaded with "trusted-content" > in it. So if we rename it now, we will need to support both > spellings, via defvaralias. I'm not sure the problem is acute enough > to justify such last-minute changes. Do we really maintain backwards-compatibility with all pretest releases also? I usually consider them more like development branches: used for testing, not for production. In any case, I think using the right word is better, so if we need a defvaralias then so be it, IMO. I don't see how it could hurt, and we could even define-obsolete-variable-alias. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Please rename trusted-content to trusted-contents 2024-12-20 9:42 ` Stefan Kangas @ 2024-12-20 12:30 ` Eli Zaretskii 0 siblings, 0 replies; 4+ messages in thread From: Eli Zaretskii @ 2024-12-20 12:30 UTC (permalink / raw) To: Stefan Kangas; +Cc: rms, emacs-devel > From: Stefan Kangas <stefankangas@gmail.com> > Date: Fri, 20 Dec 2024 04:42:31 -0500 > Cc: emacs-devel@gnu.org > > Eli Zaretskii <eliz@gnu.org> writes: > > >> From: Richard Stallman <rms@gnu.org> > >> Date: Fri, 20 Dec 2024 00:23:32 -0500 > >> > >> "Contents" and "content" are two different words, and for this > >> meaning, "contents" is correct. It means the contents of the > >> file, and that's what we refer to here. > >> > >> Please let's rename that symbol now before it gets into a release. > > > > The Emacs 30.0.93 pretest was already uploaded with "trusted-content" > > in it. So if we rename it now, we will need to support both > > spellings, via defvaralias. I'm not sure the problem is acute enough > > to justify such last-minute changes. > > Do we really maintain backwards-compatibility with all pretest releases > also? I usually consider them more like development branches: used for > testing, not for production. We don't usually maintain compatibility in those cases, but this situation is special: we are very close to the release, and I don't want to waste one more pretest because we renamed the variable. > In any case, I think using the right word is better, so if we need a > defvaralias then so be it, IMO. I don't see how it could hurt, and we > could even define-obsolete-variable-alias. From where I stand, if we decide to rename it, we must have a defvaralias for the other name. And FWIW, renaming doesn't sound very important to me: Emacs is full of mis-spellings and English usage that is not 110% correct, so I don't see this as a catastrophe. After all, Stefan's English is either his first language or close, so if he is okay with that name, we are not in a bad place. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-12-20 12:30 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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
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).