From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-24 r117559: Fix bug #18636 with documentation of multi-monitor displays.
Date: Thu, 09 Oct 2014 22:17:32 +0200 [thread overview]
Message-ID: <87ppe13smb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: xk4mvd2gfa.fsf@fencepost.gnu.org
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
Glenn Morris <rgm@gnu.org> writes:
> It also says:
>
> It would be straightforward to extend Texinfo to work in a
> similar fashion for C, Fortran, or other languages.
>
> (All the cool, hip languages!)
>
> The fact that no-one ever bothered, and that @lisp is used a grand total
> of 16 times in the Emacs Lisp Reference manual, indicates to me that
> this feature is... pointless. But YMMV.
dak@lola:/usr/local/tmp/lilypond$ git grep '@lilypond' Documentation|wc -l
9097
And indeed, the @lilypond passages are extracted and compiled separately
as LilyPond code, then the images are reinserted into the output.
With an input like
@node String number indications
@unnumberedsubsubsec String number indications
@cindex string numbers
@cindex string vs. fingering numbers
@cindex fingering vs. string numbers
The string on which a note should be played may be indicated by
appending @code{\@var{number}} to a note.
@lilypond[verbatim,quote,relative=0]
\clef "treble_8"
c4\5 e\4 g2\3
<c,\5 e\4 g\3>1
@end lilypond
When fingerings and string indications are used together, their
placement can be controlled by the order in which the two items appear
in the code @emph{only} if they appear inside of an explicit chord:
generating output like
[-- Attachment #2: inf.png --]
[-- Type: image/png, Size: 33119 bytes --]
[-- Attachment #3: Type: text/plain, Size: 281 bytes --]
or the web page
<URL:http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-fretted-strings#string-number-indications>
So while the idea might not have caught on in general, in LilyPond's
documentation it is used several thousands of times.
--
David Kastrup
next prev parent reply other threads:[~2014-10-09 20:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XboJj-0000jY-D1@vcs.savannah.gnu.org>
2014-10-08 19:52 ` [Emacs-diffs] emacs-24 r117559: Fix bug #18636 with documentation of multi-monitor displays Glenn Morris
2014-10-08 20:03 ` Eli Zaretskii
2014-10-08 21:31 ` Stefan Monnier
2014-10-09 5:37 ` Jan Djärv
2014-10-09 7:09 ` Eli Zaretskii
2014-10-09 7:32 ` Eli Zaretskii
2014-10-09 15:56 ` Glenn Morris
2014-10-09 17:18 ` Eli Zaretskii
2014-10-09 17:45 ` Glenn Morris
2014-10-09 17:57 ` Eli Zaretskii
2014-10-09 19:26 ` Glenn Morris
2014-10-09 20:17 ` David Kastrup [this message]
2014-10-09 21:04 ` Stefan Monnier
2014-10-09 21:29 ` David Kastrup
2014-10-11 1:14 ` Richard Stallman
2014-10-11 7:51 ` David Kastrup
[not found] ` <<83vbnuib0y.fsf@gnu.org>
2014-10-08 20:16 ` Drew Adams
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=87ppe13smb.fsf@fencepost.gnu.org \
--to=dak@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 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.