All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: Glenn Washburn <development@efficientek.com>
Cc: grub-devel@gnu.org, Daniel Kiper <dkiper@net-space.pl>,
	Olaf Hering <olaf@aepfle.de>
Subject: Re: [PATCH 1/2] docs: Use @pxref instead of @xref inside parenthesis
Date: Sat, 19 Aug 2023 20:57:45 -0500	[thread overview]
Message-ID: <ZOFzGaOOvrEOyAdt@dj3ntoo> (raw)
In-Reply-To: <d85c7efc568196cd0e15f8d22bbdd6f81fd32a88.1692426184.git.development@efficientek.com>


[-- Attachment #1.1: Type: text/plain, Size: 1995 bytes --]

On Sat, Aug 19, 2023 at 01:25:16 -0500, Glenn Washburn wrote:
> The @xref command is meant to be used at the beginning of a sentence
> because its expansion creates a "See " prefix. The @pxref expands with
> a prefix of "see " and is meant to be used within parenthesis. This also
> fixes an issue where there was a repeated "see" in the output.

I'm not quite convinced this is correct.

The original looks like this when viewed in info(1):

    It will read all configuration scripts as if booting directly (see
    *Note Loading an operating system directly::).

With your patch applied it looks like this:

    It will read all configuration scripts as if booting directly (*note
    Loading an operating system directly::).

According to Texinfo docs on @pxref [1], it will expand out to "see
[...]" in a printed manual only. It even recommends using this to make
it clear (and visible in info) that "see" is part of the rendered text:

    see @ref{node-name}

> 
> Reported-by: Olaf Hering <olaf@aepfle.de>
> Signed-off-by: Glenn Washburn <development@efficientek.com>
> ---
>  docs/grub.texi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/docs/grub.texi b/docs/grub.texi
> index 61e9a0e9ebf8..8da5c3f359c5 100644
> --- a/docs/grub.texi
> +++ b/docs/grub.texi
> @@ -956,7 +956,7 @@ information.
>  @subsection Kexec with grub2-emu
>  
>  GRUB can be run in userspace by invoking the grub2-emu tool. It will
> -read all configuration scripts as if booting directly (see @xref{Loading
> +read all configuration scripts as if booting directly (@pxref{Loading

Making this "see @ref" instead of "@pxref" keeps the "see" when viewed
in info and hopefully also fixes Olaf's "@xref in parentheses" issue:

    It will read all configuration scripts as if booting directly (see
    *note Loading an operating system directly::).

- Oskari

[1]: https://www.gnu.org/software/texinfo/manual/texinfo-html/_0040pxref.html

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

  reply	other threads:[~2023-08-20  1:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-19  6:25 [PATCH 0/2] Fix documentation issues reported by Olaf Glenn Washburn
2023-08-19  6:25 ` [PATCH 1/2] docs: Use @pxref instead of @xref inside parenthesis Glenn Washburn
2023-08-20  1:57   ` Oskari Pirhonen [this message]
2023-08-21 19:53     ` Glenn Washburn
2023-08-19  6:25 ` [PATCH 2/2] docs: Add menu to prevent older makeinfo versions from failing Glenn Washburn
2023-08-20  2:14   ` Oskari Pirhonen

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=ZOFzGaOOvrEOyAdt@dj3ntoo \
    --to=xxc3ncoredxx@gmail.com \
    --cc=development@efficientek.com \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=olaf@aepfle.de \
    /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.
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.