From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: philipk@posteo.net, emacs-devel@gnu.org, johnw@gnu.org
Subject: Re: use-package has been merged into emacs-29
Date: Mon, 12 Dec 2022 05:25:14 +0100 [thread overview]
Message-ID: <CADwFkmnr9H-J-kWjkXJ=n_-_8i0noFPuJ-doz2wtQV5GA8Xsbg@mail.gmail.com> (raw)
In-Reply-To: <83tu21s372.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> > (There's also @sc, if @acronym is too jarring.)
>
> Yes, but that'd have to be applied consistently.
Agreed. The most important thing is to be consistent.
> > > 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?
>
> @acronym doesn't produce small caps.
Sorry, you're right. The docs says that "the acronym is printed in
slightly smaller font" (in TeX).
next prev parent reply other threads:[~2022-12-12 4:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 18:59 use-package has been merged into emacs-29 Stefan Kangas
2022-12-08 22:17 ` John Wiegley
2022-12-09 16:09 ` Philip Kaludercic
2022-12-09 16:18 ` Eli Zaretskii
2022-12-09 17:06 ` Philip Kaludercic
2022-12-09 19:00 ` Eli Zaretskii
2022-12-09 16:23 ` Eli Zaretskii
2022-12-09 16:26 ` Eli Zaretskii
2022-12-10 20:34 ` Stefan Kangas
2022-12-11 6:25 ` Eli Zaretskii
2022-12-12 1:19 ` Stefan Kangas
2022-12-12 3:36 ` Eli Zaretskii
2022-12-12 4:25 ` Stefan Kangas [this message]
2022-12-11 22:11 ` Philip Kaludercic
2022-12-12 1:19 ` Stefan Kangas
2022-12-12 20:21 ` Philip Kaludercic
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 2:11 Payas Relekar
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='CADwFkmnr9H-J-kWjkXJ=n_-_8i0noFPuJ-doz2wtQV5GA8Xsbg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=philipk@posteo.net \
/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).