all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: stefankangas@gmail.com, emacs-devel@gnu.org, johnw@gnu.org
Subject: Re: use-package has been merged into emacs-29
Date: Fri, 09 Dec 2022 21:00:30 +0200	[thread overview]
Message-ID: <83bkocz9kh.fsf@gnu.org> (raw)
In-Reply-To: <874ju4cxs5.fsf@posteo.net> (message from Philip Kaludercic on Fri, 09 Dec 2022 17:06:02 +0000)

> From: Philip Kaludercic <philipk@posteo.net>
> Cc: stefankangas@gmail.com,  emacs-devel@gnu.org,  johnw@gnu.org
> Date: Fri, 09 Dec 2022 17:06:02 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > What is the problem with "see @ref"?
> 
> If you are asking, I am assuming I am wrong.  My assumption was that
> @pxref was preferable.

It is preferable when the cross-reference ends in a closing
parenthesis.  The case you are referring to has more text after the
cross-reference and before the closing parenthesis, right?

> > Thanks, but there's no need to post such comments: just go ahead and
> > fix what needs to be fixed.  People who work on these changes are not
> > angels: we make mistakes, and appreciate when others silently fix them
> > when they spot them.
> 
> I am sorry if my comments had a negative tone -- I am certainly no
> texinfo expert, so I'd rather discuss the questions before applying any
> changes.

You can consider yourself an expert, since you've uncovered the
problems and inconsistencies.

> >> - Some packages are formatted as @file's (hydra, ivy, diminish, delight,
> >>   ...).  Does this really make sense?
> >
> > A package is usually a file, so @file is correct.  But sometimes the
> > context is talking about a feature, and then @code or @samp is better.
> 
> I have also noticed there are a few instances of @file{<...>.el} vs
> @file{<...>}.  Perhaps it makes sense to use @file when referring to the
> packages as file names, and @code/@samp when referring to the package
> name (if at all -- just like with my question whether use-package should
> be formatted or not).

That was more or less what I tried to do.  But maybe I missed a few
places -- it's a large manual.



  reply	other threads:[~2022-12-09 19:00 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bkocz9kh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@gnu.org \
    --cc=philipk@posteo.net \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.