all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: emacs-devel@gnu.org, karl@freefriends.org
Subject: Info *note xxx* problems (WAS: mention Info image support in NEWS?)
Date: Fri, 23 Apr 2004 11:30:17 +0200	[thread overview]
Message-ID: <87k707f3di.fsf_-_@peder.flower> (raw)
In-Reply-To: <873c6xaq3b.fsf@mail.jurta.org> (Juri Linkov's message of "Thu, 22 Apr 2004 03:06:17 +0300")

Juri Linkov writes:

> I installed your additions to NEWS.

Thanks.

> I'd say GNU LilyPond Info pages with images are very nice looking!

Yes, I think so too.  I'm glad you like them.

> 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.

Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

  reply	other threads:[~2004-04-23  9:30 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   ` Jan Nieuwenhuizen [this message]
2004-04-25  4:34     ` Info *note xxx* problems Juri Linkov
2004-04-25 17:28       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k707f3di.fsf_-_@peder.flower \
    --to=janneke@gnu.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 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.