all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: larsi@gnus.org, 37078@debbugs.gnu.org
Subject: bug#37078: 27.0.50; Proposal: new introductory section to the Gnus manual
Date: Sat, 25 Jul 2020 09:11:24 +0300	[thread overview]
Message-ID: <838sf8dsz7.fsf@gnu.org> (raw)
In-Reply-To: <87h7twaaez.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Fri, 24 Jul 2020 14:08:20 -0700)

> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Cc: larsi@gnus.org,  37078@debbugs.gnu.org
> Date: Fri, 24 Jul 2020 14:08:20 -0700
> 
> > "See @pxref" again.
> >
> >> +per-group (see @pxref{Mail Sources} for more information).
> >
> > Same here.
> 
> Okay there's something funny going on here. When I run "make" with this
> exact diff, the output looks exactly right: "See _Finding the News_ for
> details." Same with your other, later notes. If I "C-x C-f" from the
> info manual (now I'm in "<emacsbuilddir>/info/") and open gnus.info, I
> see there is no "See" in the text, just "*note Finding the News:: for
> details."
> 
> Playing with this further, the info display seems to be inserting a
> "see" if there isn't one, and not if there is.

That's right, you need to look at the file itself, or reset
Info-hide-note-references to nil inside Info.

> In the info manual for the texinfo package on my system, it says all
> three reference commands (@xref, @ref, and @pxref) will insert a see.

I think you are misinterpreting the Texinfo manual, or maybe judging
by the Info mode display, not the real Info file.  In the Info format,
the cross-reference marker is "*note ", not "See".  The latter appears
in the printed manual.  And @ref doesn't generate "see" in the printed
manual, it leaves that to you, so that you could, for example, say
something like "this-and-that, as described in @ref{foo}".

> I'm not seeing any doubled "see"s in the output, though.

You should see "see *note " in the output, which is already a sign of
trouble.  And in printed output, you will see a duplicate "see".

> The texinfo package version on Arch linux is 6.7-3. Could behavior be
> different between versions?

Not this one, no.

> Anyway, I've edited my diff according to your notes, please take a look.

Mostly okay, see below.

> +using interactive commands in the Server buffer.  @ref{Finding
> +the News} for details.                            ^^^^

You want @xref here, and please remember the comma after the closing
brace.

> +messages, see @ref{Summary Mail Commands} for details.
                                            ^
A comma there is missing.





  reply	other threads:[~2020-07-25  6:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18 23:22 bug#37078: 27.0.50; Proposal: new introductory section to the Gnus manual Eric Abrahamsen
2019-08-27  2:04 ` Stefan Kangas
2019-10-22 14:27 ` Lars Ingebrigtsen
2019-10-22 19:58   ` Eric Abrahamsen
2020-07-19 15:39     ` Lars Ingebrigtsen
2020-07-20  5:28       ` Eric Abrahamsen
2020-07-20  9:48         ` Lars Ingebrigtsen
2020-07-20 18:02           ` Eric Abrahamsen
2020-07-22 20:16             ` Eric Abrahamsen
2020-07-23 13:03               ` Eli Zaretskii
2020-07-23 15:13                 ` Robert Pluim
2020-07-23 15:29                   ` Eric Abrahamsen
2020-07-23 16:59                 ` Eric Abrahamsen
2020-07-23 17:43                   ` Eli Zaretskii
2020-07-24 18:49                     ` Eric Abrahamsen
2020-07-24 19:08                       ` Eli Zaretskii
2020-07-24 21:08                         ` Eric Abrahamsen
2020-07-25  6:11                           ` Eli Zaretskii [this message]
2020-07-27 22:32                             ` Eric Abrahamsen
2020-07-27 21:48                       ` Lars Ingebrigtsen

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=838sf8dsz7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37078@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=larsi@gnus.org \
    /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.