From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org, John Wiegley <johnw@gnu.org>
Subject: Re: use-package has been merged into emacs-29
Date: Sun, 11 Dec 2022 22:11:22 +0000 [thread overview]
Message-ID: <87ilihvbed.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmnJ6OaDQ-USm_Ddwd6_YVqcLGJ=Tcs6BFZWV==ZANBj6A@mail.gmail.com> (Stefan Kangas's message of "Sat, 10 Dec 2022 12:34:03 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
>> - It appears that use-package is sometimes formatted using @code and
>> sometimes not. I can't make out a consistent rule.
>
> I've tried to follow this:
>
> - Format use-package with no markup when referring to the package.
> - Use @code{use-package} when referring to a macro call.
>
> Does that make sense?
That does make sense, but I believe to have had found instances where
this was not the case. I'll try and see if I can locate those again.
Also, this ties into the other point about the usage of @file.
Shouldn't the first case be wrapped in @file?
next prev parent reply other threads:[~2022-12-11 22:11 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
2022-12-11 22:11 ` Philip Kaludercic [this message]
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=87ilihvbed.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=stefankangas@gmail.com \
/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).