unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 b4f47d2: Use @pxref when necessary
Date: Thu, 25 Nov 2021 11:52:27 +0200	[thread overview]
Message-ID: <837dcw7eas.fsf@gnu.org> (raw)
In-Reply-To: <87a6hsh9t1.fsf@gmail.com> (message from Robert Pluim on Thu, 25 Nov 2021 10:19:22 +0100)

> From: Robert Pluim <rpluim@gmail.com>
> Date: Thu, 25 Nov 2021 10:19:22 +0100
> Cc: emacs-devel@gnu.org
> 
>     Eli> This problem should be fixed in info.el, not in the Texinfo sources.
>     Eli> (It should have been mentioned in the log message as well, btw.)
>     Eli> There's nothing wrong with "see @ref" from the Texinfo usage
>     Eli> POV.
> 
> This is "(see @ref", not "see @ref". The latter works correctly. Maybe
> this can be fixed in info.el as you say (it would certainly clean up
> the display of org.info).

So I guess it's this part of info.el that needs to become smarter:

              (when Info-hide-note-references
                (when (and (not (eq Info-hide-note-references 'hide))
                           (> (line-number-at-pos) 4)) ; Skip breadcrumbs
                  ;; *Note is often used where *note should have been
                  (goto-char start)
                  (skip-syntax-backward " ")
		  (when (memq (char-before) '(?\( ?\[ ?\{))
		    ;; Check whether the paren is preceded by
		    ;; an end of sentence
		    (skip-syntax-backward " ("))
                  (setq other-tag
			(cond ((save-match-data (looking-back "\\(^\\| \\)see"
                                                              (- (point) 4)))
			       "")
			      ((save-match-data (looking-back "\\(^\\| \\)in"
                                                              (- (point) 3)))
			       "")
			      ((memq (char-before) '(nil ?\. ?! ??))
                               "See ")
			      ((save-match-data
				 (save-excursion
				   (search-forward "\n\n" start t)))
			       "See ")
			      (t "see "))))



  reply	other threads:[~2021-11-25  9:52 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 [this message]
2021-11-25 10:18           ` Robert Pluim
2021-11-25 10:53             ` Eli Zaretskii
2021-11-25 14:38               ` Robert Pluim
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=837dcw7eas.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@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).