unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 b4f47d2: Use @pxref when necessary
Date: Thu, 25 Nov 2021 15:38:02 +0100	[thread overview]
Message-ID: <8735nk712t.fsf@gmail.com> (raw)
In-Reply-To: <83zgps5wwi.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 Nov 2021 12:53:33 +0200")

>>>>> On Thu, 25 Nov 2021 12:53:33 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Robert Pluim <rpluim@gmail.com>
    >> Cc: emacs-devel@gnu.org
    >> Date: Thu, 25 Nov 2021 11:18:03 +0100
    >> 
    >> >>>>> On Thu, 25 Nov 2021 10:19:22 +0100, Robert Pluim <rpluim@gmail.com> said:
    Robert> This is "(see @ref", not "see @ref". The latter works correctly. Maybe
    Robert> this can be fixed in info.el as you say (it would certainly clean up
    Robert> the display of org.info).
    >> 
    >> Something like this, with 'Also *note'/'See also *note' as a bonus,
    >> although that might be going a bit far.

    Eli> "Also *note" that comes from "Also @ref" should be fine.  If you mean
    Eli> "Also see @ref", which currently produces "Also see see", then yes, it
    Eli> should be fixed as well.

Not quite:

Before:

Texi                  Info display

"Also @ref"        => "Also see <link>"
"See @ref"         => "See <link>"
"Also see @ref"    => "Also see <link>"
"See also @ref"    => "See also see <link>"
"(Also @ref)"      => "(Also see <link>)"
"(See @ref)"       => "(See see <link>)"
"(Also see @ref)"  => "(Also see <link>)"
"(See also @ref)"  => "(See also see <link>)"

After:

"Also @ref"        => "Also see <link>"
"See @ref"         => "See <link>"
"Also see @ref"    => "Also see <link>"
"See also @ref"    => "See also <link>"
"(Also @ref)"      => "(Also see <link>)"
"(See @ref)"       => "(See <link>)"
"(Also see @ref)"  => "(Also see <link>)"
"(See also @ref)"  => "(See also <link>)"

    Eli> Anyway, if this fixes the Org manual, feel free to install on master,
    Eli> and thanks.

The org texi generation always produces @ref, even inside parens, so I
think itʼs the best we can do.

Robert
-- 



  reply	other threads:[~2021-11-25 14:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 19:39 emacs-28 b4f47d2: Use @pxref when necessary Eli Zaretskii
2021-11-25  8:20 ` Robert Pluim
2021-11-25  8:44   ` Eli Zaretskii
2021-11-25  8:47     ` Robert Pluim
2021-11-25  9:03       ` Eli Zaretskii
2021-11-25  9:19         ` Robert Pluim
2021-11-25  9:52           ` Eli Zaretskii
2021-11-25 10:18           ` Robert Pluim
2021-11-25 10:53             ` Eli Zaretskii
2021-11-25 14:38               ` Robert Pluim [this message]
2021-11-25 16:54                 ` Eli Zaretskii
2021-11-25 17:15                   ` Robert Pluim

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=8735nk712t.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 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).