[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] emacs-24 r117559: Fix bug #18636 with documentation of

From: David Kastrup
Subject: Re: [Emacs-diffs] emacs-24 r117559: Fix bug #18636 with documentation of multi-monitor displays.
Date: Sat, 11 Oct 2014 09:51:37 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux)

Richard Stallman <address@hidden> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> It might be good to create a Texinfo command that is like @example
> but treats braces as ordinary characters.

@verbatim is more or less like that, or at least you can combine it with
@quote.  Due to its implementation in TeX, it cannot really be used as a
building block for macros you define yourself.  It's only useful as a
direct user input command.

> Lilypond could define @lilypond an alias for that command.

Since lilypond-book (the application converting files with @lilypond
commands in them into proper Texinfo input) needs to insert the @image
commands pointing to the graphics from processing the content in the
@lilypond command into the actually generated Texinfo input, Texinfo
does not get to see the original environment anyway.

The actually generated input already uses @verbatim and looks something

@exampleindent 0
bass = {
  \clef bass
  g4 b, c d
  e d8 c d2

continuo = \figuremode {
  <_>4 <6>4 <5/>4
  \override Staff.BassFigureAlignmentPositioning.direction = #UP
  < _+ >4 <6>
  \set Staff.useBassFigureExtenders = ##t
  \override Staff.BassFigureAlignmentPositioning.direction = #DOWN
  <4>4. <4>8 <_+>4

\score {
    \new Staff = bassStaff \bass
    \context Staff = bassStaff \continuo
@end verbatim
@image{34/lily-fdcff975,,,[image of music],}
@end ifinfo
 <a href="34/lily-fdcff975.ly">
  <img align="middle"
       alt="[image of music]">
@end html

@include 34/lily-fdcff975-systems.texi
@end iftex

Richard, if you treat every example of a working system that somebody
brings up in the course of a discussion as a request for letting you
redesign stuff that has been working for decades to the satisfaction of
its users rather than as input to the discussion, the discussion can go

It's fine to explore possible fundamental deficiencies and its effects
on system and users concerning the aspects under discussion, but when
some particular tangent has veered off completely from the topic of
discussion and the list, it would make sense to continue it, if at all,
in private communication.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]