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: use-package has been merged into emacs-29 Date: Sun, 11 Dec 2022 08:25:09 +0200 Message-ID: <83sfhmv4my.fsf@gnu.org> References: <878rjgd0ej.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38708"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, emacs-devel@gnu.org, johnw@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 11 07:25:42 2022 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 1p4FmP-0009s6-72 for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Dec 2022 07:25:41 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p4Flx-0003mR-8m; Sun, 11 Dec 2022 01:25:13 -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 1p4Flw-0003mI-5S for emacs-devel@gnu.org; Sun, 11 Dec 2022 01:25:12 -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 1p4Flv-0008RH-Lr; Sun, 11 Dec 2022 01:25:11 -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=fWl/I4hopxDa1r637R5tyUTIFFiaF1XKRgEMIwrlcZM=; b=FJRe0238sVyJ KS+orwnEf0c7QJz9Xm83rIUeA08VAMjcRbCYoOqs0iitmE4xTglTDwhwIT1gaweP12QVo2MSe4Tci w09P3IiKHhv20f+KrmOI2fW4T9PZnQCZsWmxBhosI2n19RTXBLd85ygZmG3Xfy3o9LIS6u0mFtFJr fvSEheU4eFSt2eAXeKubN6wLFKMb8pbzB84lkLIncmwL4Ly0mYqScY5L0nIW0F5ZXDbu4r6HMcb4f 5XL8KN72PzxWEcD/TQA2qujo2k1u8yVSISV7+tfKM0bWrtUYGAoK16ZAB4bLNuwDgwj9qJCLUwI+O 9H8c4BJHAeiQ1ai0zqDZ8g==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p4Flu-00059G-SA; Sun, 11 Dec 2022 01:25:11 -0500 In-Reply-To: (message from Stefan Kangas on Sat, 10 Dec 2022 12:34:03 -0800) 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:301142 Archived-At: > From: Stefan Kangas > Date: Sat, 10 Dec 2022 12:34:03 -0800 > Cc: emacs-devel@gnu.org, John Wiegley > > In one sense, @acronym{GNU ELPA} is better, as that is the full name. > One way of looking at it is that the acronym for "GNU Emacs Lisp Package > Archive" is actually the acronym "GNUELPA", which we just happen to > typeset with a space for increased legibility. Please don't make @acronym have more than one word. I tried to fix those cases, but maybe I missed some. It should be "@acronym{GNU} @acronym{ELPA}" instead. > But we also have @acronym{NonGNU ELPA}, and I guess we are now looking > at just a name that is not really an acronym at all? So perhaps we > should just write out the names GNU ELPA and NonGNU ELPA without any > markup? Because we also don't want "@acronym{NonGNU} @acronym{ELPA}", I > suppose? It should be "NonGNU @acronym{ELPA}", I think.