unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Earl <jearl@notengoamigos.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 8398@debbugs.gnu.org
Subject: bug#8398: 24.0.50; info-mode adding spurious "see" to @ref links
Date: Fri, 01 Apr 2011 13:26:00 -0600	[thread overview]
Message-ID: <87hbah6aev.fsf@notengoamigos.org> (raw)
In-Reply-To: <y62qystq0.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 31 Mar 2011 20:25:43 -0400")

On Thu, Mar 31 2011, Glenn Morris wrote:

> Jason Earl wrote:
>
>> For more information on info itself you can read
>> @iftex
>> @cite{Info: An Introduction}.
>> @end iftex
>> @ifnottex
>> @ref{Top, , Info, info, Info: An Introduction}.
>> @end ifnottex
>>
>> The info file produced, and it looked fine in the info client.
>>
>>    For more information on info itself you can read *note Info:
>> (info)Top.
>>
>> However, in Emacs' info-mode it looks like this:
>>
>>    For more information on info itself you can read *note Info:
>> (info)Top.
>>
>> Essentially it replaced the *note with the word "see" which makes the
>> sentence read funny.
>
> I think you mis-typed your second example...
>
> The behaviour is customizable through Info-hide-note-references.
>
> The elisp intro does not say "you can read", so looks OK IMO:
>
>    This introduction to `Programming in Emacs Lisp' has a companion
> document, see The GNU Emacs Lisp Reference Manual.
>
> Personally I think your "you can read @ref" is not really Texinfo style (?),
> which is why the result looks a bit odd.
>
> http://www.gnu.org/s/hello/manual/texinfo/ref.html

I am sorry for the noise.  I borrowed the Texinfo from the /Emacs Lisp
Intro/ (it seemed like a safe bet), and then the output appeared
differently in Emacs and the info file reader, so I thought it might be
a bug.

I am starting to realize that borrowing examples from the /Emacs Lisp
Intro/ is not a good idea.  This is the second time that has bitten me.

I will reword my Texinfo source and call it good.  Thanks for looking
into this, and, once again, sorry for the noise.

Jason Earl





  parent reply	other threads:[~2011-04-01 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 17:53 bug#8398: 24.0.50; info-mode adding spurious "see" to @ref links Jason Earl
2011-04-01  0:25 ` Glenn Morris
2011-04-01  7:55   ` Eli Zaretskii
2011-04-01 19:26   ` Jason Earl [this message]
2011-04-01 22:41     ` Glenn Morris

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=87hbah6aev.fsf@notengoamigos.org \
    --to=jearl@notengoamigos.org \
    --cc=8398@debbugs.gnu.org \
    --cc=rgm@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).