[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: use-package has been merged into emacs-29
From: |
Stefan Kangas |
Subject: |
Re: use-package has been merged into emacs-29 |
Date: |
Sun, 11 Dec 2022 17:19:35 -0800 |
Eli Zaretskii <eliz@gnu.org> writes:
> 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.
(There's also @sc, if @acronym is too jarring.)
>> 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.
Then half the name will be in smallcaps and the other one won't be,
right? Doesn't that seem a bit unusual?
My preference here would probably be to just use the names with no
markup, just as we do with e.g. GNU/Linux. We do that even if the first
half of that name is an acronym. Would that work?
- use-package has been merged into emacs-29, Stefan Kangas, 2022/12/08
- Re: use-package has been merged into emacs-29, John Wiegley, 2022/12/08
- Re: use-package has been merged into emacs-29, Philip Kaludercic, 2022/12/09
- Re: use-package has been merged into emacs-29, Eli Zaretskii, 2022/12/09
- Re: use-package has been merged into emacs-29, Eli Zaretskii, 2022/12/09
- Re: use-package has been merged into emacs-29, Stefan Kangas, 2022/12/10
- Re: use-package has been merged into emacs-29, Philip Kaludercic, 2022/12/11
- Re: use-package has been merged into emacs-29, Stefan Kangas, 2022/12/11
- Re: use-package has been merged into emacs-29, Philip Kaludercic, 2022/12/12