From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Please rename trusted-content to trusted-contents Date: Fri, 20 Dec 2024 14:30:14 +0200 Message-ID: <86ikrea65l.fsf@gnu.org> References: <86cyhmkczw.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37694"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 20 13:31:18 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tOcA1-0009am-Q6 for ged-emacs-devel@m.gmane-mx.org; Fri, 20 Dec 2024 13:31:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tOc9J-00060z-JG; Fri, 20 Dec 2024 07:30:33 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tOc9H-0005xf-Rc for emacs-devel@gnu.org; Fri, 20 Dec 2024 07:30:32 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tOc9H-0008PC-Hy; Fri, 20 Dec 2024 07:30:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=IAevGA8XH9eK1NQDgziuJoibs/FFtOGs9MzcflLNoNM=; b=XddcjONN3XkK Dt68HuKcQDcjmrefnyKqCXtEwcuYCPFmOKj2UQKCd90NeIoR9DtJQJJJmbR4UhmTaPQ9ljqwNGjjQ JtJYMC+kAJBko3HqAeqIwG6DU5zOnebOFmVzXWwZfdxopH5BnxY/hVkO0q6D5ncXo+xs+5KVXYTSp KulSArZtQoV1mxBI1lZhH/aoqVpPU83Pt0uQvxx+0pQK24JHuv3yZiGarb1g9SlCHFrvF/XtDMhyX WQam0JY9lAotVa6QEqXgKcTJds8M8aEbotCinYnC4eYhzIk6iUw4txp3vNya0sB57WcByaWmxHLHw HKMJQolKZvEbiQmAHZovHw==; In-Reply-To: (message from Stefan Kangas on Fri, 20 Dec 2024 04:42:31 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:326798 Archived-At: > From: Stefan Kangas > Date: Fri, 20 Dec 2024 04:42:31 -0500 > Cc: emacs-devel@gnu.org > > Eli Zaretskii writes: > > >> From: Richard Stallman > >> 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.