Werner LEMBERG wrote:
How about @[EMAIL PROTECTED] }} instead? I think that actual input should
be in a monospace font, and these commands nest without problem.
This is redundant -- @samp{} already produces fixed-width output.
Oops, I didn't realize that.
In that case, I don't think that @s
> How about @[EMAIL PROTECTED] }} instead? I think that actual input should
> be in a monospace font, and these commands nest without problem.
This is redundant -- @samp{} already produces fixed-width output.
Werner
___
lilypond-devel mailing l
2007/10/9, Ralph Little <[EMAIL PROTECTED]>:
> Hi,
> Can anybody help me with what the group of functions surrounding:
>
> precomputed_recurse_over_translators() and
> Translator_group::precompute_method_bindings()
we have all these functions like
Foo_engraver::start_translation_timestep()
we c
2007/10/9, Ralph Little <[EMAIL PROTECTED]>:
> Hi,
> Sorry for my C++ ignorance, but what does the following do?
>
> =
> void
> performer_each (SCM list, Performer_method method)
> {
> for (SCM p = list; scm_is_pair (p); p = scm_cdr (p))
> {
> Per
2007/10/9, Ralph Little <[EMAIL PROTECTED]>:
> Hi,
> More strangeness.
>
> In Performer_group::do_announces(), there is this:
> ==
> while (1)
> {
> performer_each (get_simple_trans_list (),
> &Performer::create_audio_elements);
>
> if
I meant PhD students starting to use lilypond ! (me too)
R
On 9 Oct 2007, at 20:13, Ricardo Climent wrote:
Dear Lilypond developers,
Could you please forward this to the users list?
I am sorry I am only subscribed to this one. I hope NOVARS to be of
your interest; I already have some PhD s
Werner LEMBERG wrote:
@code{}: actual lilypond code or property/context names.
@samp{}: refers to pieces of notation, such as: @samp{crescendo} is
often abbreviated as @samp{cresc.}.
Sounds fine. Actually, I've always tried to clean up the code
accordingly. However, sometimes it's better IM
Dear Lilypond developers,
Could you please forward this to the users list?
I am sorry I am only subscribed to this one. I hope NOVARS to be of
your interest; I already have some PhD students starting to use it.
Best,
Ricardo
--
MANTIS Presents: NOVARS LAUNCH FESTIVAL, Universi
As far as I know, this macro has never been defined by default. How did
you get the impression that it was?
All the examples I could find on the web when Googling for lilypond noFlag
include a definition of that macro at the top of the file. For example
http://lilypond.org/doc/v2.11/Documentatio
2.11.33 is missing \noFlag.
I had to use
\override Stem #'flag-style = #'no-flag
instead.
Stephen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
More strangeness.
In Performer_group::do_announces(), there is this:
==
while (1)
{
performer_each (get_simple_trans_list (),
&Performer::create_audio_elements);
if (!announce_infos_.size ())
break;
acknowledge_audio_element
El Mon, 08 de Oct de 2007, a las 01:11:18PM -0700, Graham Percival dijo:
> Han-Wen Nienhuys wrote:
> >2007/10/8, Graham Percival <[EMAIL PROTECTED]>:
> >>I believe that this info is outdated, and that point-and-click info is
> >>stored in pdfs which automatically load the text editor. Or something
12 matches
Mail list logo