On Thu 03 Jun 2010, 20:52 Graham Percival wrote:
> Hi Bug Squad and others,
>
> I've updated CG 7 Issues:
> http://lilypond.org/doc/v2.13/Documentation/contributor/issues
7.1 Introduction to issues and the Bug Squad
1. "If the behaviour is expected, the user should be told to read the
documentat
On Fri, Jun 4, 2010 at 6:35 AM, James Bailey
wrote:
>
> Two reasons I like already having a tiny example:
> 1) It's frequently easier to understand a problem if a tiny example has
> already been provided.
> 2) It helps to make sure that the problem submitted is an actual problem;
> i.e., the perso
On Fri, Jun 4, 2010 at 8:05 AM, Dmytro O. Redchuk
wrote:
> 1. "If the behaviour is expected, the user should be told to read the
> documentation"...
>
> Isn't it a task for "Support" team? If i asked smth. like mentioned here in
> bug-lilypond, i would consider as a quite normal answer "please ask
(OBS: I'm writing to user and devel lists as I am not sure if it is a
bug...)
Hello,
I am trying to generate svg files of my score, where I use some
\postscript markups. Everything goes ok, except those markups...
I get this warning and the svg file comes without the postcript drawings...
"wa
> Note that this description isn't correct anymore. This patch doesn't
actually prevent those functions from segfaulting but adds a new
interface ly:parser-include-string. I think ly:parser-parse-string and
ly:parser-parse-file should actually be banned in .ly files.
If ly:parser-include-strin
2010/6/4 :
> > Note that this description isn't correct anymore. This patch doesn't
>>
>> actually prevent those functions from segfaulting but adds a new
>> interface ly:parser-include-string. I think ly:parser-parse-string and
>> ly:parser-parse-file should actually be banned in .ly files.
>
>
2010/6/4 josé henrique padovani :
>
> I am trying to generate svg files of my score, where I use some \postscript
> markups. Everything goes ok, except those markups...
> I get this warning and the svg file comes without the postcript drawings...
> "warning: missing stencil expression `embedded-ps'
>>> \relative c' {
>>> \override Fingering #'text =
>>> #(lambda (grob)
>>> (let ((finger-text (ly:event-property (event-cause grob) 'text)))
>>> (if (markup? finger-text)
>>> finger-text
>>> (fingering::calc-text grob
>>> c4
2010/6/4 Frédéric Bron :
> added to issue 1029 and to LSR.
>
> What next can a frog do for this?
Hi (yeah, me again)! :)
I have no authority in development, nor in bug policy, but I have a
proposal about how to handle this issue.
Actually I think we could "divide" this issue into 2 separate o
On 6/4/10 4:04 PM, "Xavier Scheuer" wrote:
> 2010/6/4 Frédéric Bron :
>
>> added to issue 1029 and to LSR.
>>
>> What next can a frog do for this?
>
> Hi (yeah, me again)! :)
>
> I have no authority in development, nor in bug policy, but I have a
> proposal about how to handle this issue
> 1. short-term fix: change "thumb" definition (avoid-slur . around
> + add other "Fingering" properties that also exists for Script),
> but keeping \thumb engraved by "Script_engraver".
> Here is what I think could be fine:
>
> ("thumb"
> . (
> (script-stencil . (feta . ("t
11 matches
Mail list logo
