From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org, karl@freefriends.org
Subject: Re: Info *note xxx* problems
Date: Sun, 25 Apr 2004 07:34:03 +0300 [thread overview]
Message-ID: <87d65wln9c.fsf@mail.jurta.org> (raw)
In-Reply-To: <87k707f3di.fsf_-_@peder.flower> (Jan Nieuwenhuizen's message of "Fri, 23 Apr 2004 11:30:17 +0200")
Jan Nieuwenhuizen <janneke@gnu.org> writes:
> Juri Linkov writes:
>> other problem was in the LilyPond music glossary with the word
>> `*note*' emphasized by asterisks around it. This is already fixed
>> in Emacs Info reader to skip the `*note' text without whitespace
>> after it, but there are still other places in the LilyPond music
>> glossary which are interpreted as cross references:
>>
>> *note head*
>> *note value*
>>
>> As one solution you can replace a space by some other non-space character,
>> for example:
>>
>> *note_head*
>> *note-value*
>
> I would much prefer fixing the info readers, rather than mangling node
> names, if possible.
I don't see how Info readers could be fixed: the `*note ' text
is used for cross-references.
Fortunately, you can use emphasis other than asterisks by replacing
the @string argument of the @table by any argument which doesn't put
asterisks around the text: @emph, @asis, @code, @samp, @var, @option...
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-04-25 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 9:44 mention Info image support in NEWS? Jan Nieuwenhuizen
2004-04-21 18:58 ` Richard Stallman
2004-04-22 0:06 ` Juri Linkov
2004-04-23 9:30 ` Info *note xxx* problems (WAS: mention Info image support in NEWS?) Jan Nieuwenhuizen
2004-04-25 4:34 ` Juri Linkov [this message]
2004-04-25 17:28 ` Info *note xxx* problems Jan Nieuwenhuizen
2004-04-25 21:29 ` Karl Berry
2004-04-25 22:04 ` Jan Nieuwenhuizen
2004-04-26 4:48 ` Juri Linkov
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=87d65wln9c.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=karl@freefriends.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).