Isn't it an ugly collision, really?
2016-02-25 10:57 GMT+02:00 Dmytro O. Redchuk :
> Yes! Thank you for this workaround!
>
> ps. Anyway, I think this is an issue.
>
> \version "2.18.2"
>
> \score {
> \context ChoirStaff <<
> \ac
t; \context {
>> \Staff
>> \override AccidentalCautionary #'font-size = #-3
>> }
>> }
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
}
}
% -- 8< ----
Now I think this is an issue.
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
2015-12-19 8:30 GMT+02:00 Masamichi HOSODA :
>> In the case of text font, variable `font' is set to #f.
>> In the case of music font, variable `font' is set to non-#f.
>
> I've created issue 4701.
Thank you!
--
Dmytro O. Redchuk
___
(ps-load-file file-name))
+ ((string? font-file-name)
+ (ps-load-file font-file-name))
(else
(ly:warning (_ "cannot embed ~S=~S") name file-name)
""))
--
Dmytro O.
Sorry, this "patch" has huge problems .(
2015-12-08 11:44 GMT+02:00 Dmytro O. Redchuk :
> With this patch it looks like "it works for me".
>
> I will check more. What would I check besides of a "regular"
> (lilypond's and lilypond-book's)
;t know what I am doing.
Thank you!
2015-12-08 9:57 GMT+02:00 Dmytro O. Redchuk :
> 2015-12-08 9:55 GMT+02:00 Dmytro O. Redchuk :
>> Hello,
>>
>> to avoid any misunderstanding with any "include"'s I've tested this
>> issue with this source:
> And th
2015-12-08 9:55 GMT+02:00 Dmytro O. Redchuk :
> Hello,
>
> to avoid any misunderstanding with any "include"'s I've tested this
> issue with this source:
And the command was (no -I...), of course:
$ lilypond-book --out=out [--pdf] test.lytex
>
> % 8<
:music "improviso"
#:factor (/ staff-height pt 20)
))
}
\end{lilypond}
\end{document}
% 8< --
And I have the same result, attached.
2015-12-07 22:00 GMT+02:00 Dmytro O. Redchuk :
> 2015-12-07 19:55 GMT+02:00 James :
>> Hello Dmytro,
>
ib.org/improviso/, an alternate
font for lilypond).
So, without --pdf I have nice result, with --pdf I have a score(s)
with "improviso-related" objects missed.
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
2015-12-07 15:12 GMT+02:00 Dmytro O. Redchuk :
> Hello bug squad, hello list,
>
> I've found a problem with this "book":
I am sorry, forgot to mention,
tested with 2.18.2 and 2.19.32, got the same result.
>
> % test.lytex:
> % 8<
> \d
---
Now I have pdf containing a score with no clef, key signature and notehead.
I've attached png files produced by
$ convert -density 150 -1.eps -flatten -1.png
for both ways, with and without --pdf.
Is this an issue? How to work around?
Thank you!
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
g list.
Thank you, added as 1946:
http://code.google.com/p/lilypond/issues/detail?id=1946
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
__
ditional knowledge.
>
> Opera Mini seems to be ok.
Added as 1934:
http://code.google.com/p/lilypond/issues/detail?id=1934
Thank you!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
open eps
> files in Lilydev so all regtest archives from
> http://lilypond.org/download/binaries/test-output/ are useless for
> me...
I've finally added this as 1918:
http://code.google.com/p/lilypond/issues/detail?id=1918
Please, anyone, help me adjust labels.
--
Dmytro O. Redch
On Thu 22 Sep 2011, 14:06 Bertrand Bordage wrote:
> I'm ok with this subject.
>
> A better minimal example would be :
>
> \new MensuralStaff {
> \cadenzaOn
> \[ a'\breve g' as' \]
> }
Thank you, added as 1916:
http://code.google.com/p/lilypond/is
eve g as \]
> }
So, the subject "lilypond should issue a warning regarding incorrect ligature"
is ok?
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
se it (with an explanation) -- please, can anyone
prepare a tiny example?
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mai
I can add this with Needs-evidence,
to avoid it to get lost, though.
> kind regards,
> Arthur Lawrence
> PS I can send the complete score if it helps
>
> On 22 Sep 2011, at 8:38 am, Dmytro O. Redchuk wrote:
>
> > On Tue 20 Sep 2011, 11:52 a...@bflat.demon.co.uk wrote:
&
gt; this looks as if the slur goes from the e of the 2nd voice to the g of the
> 1st.
Added ad 1915:
http://code.google.com/p/lilypond/issues/detail?id=1915
Sorry, I am not sure that this is a valid issue -- I've marked it with
"Needs-evidence".
Thank you!
-
\new Staff { \mvtI }
>\header { piece = "Page 1"}
> }
>
> \myPageBreak
>
> \score {
>\new Staff { \mvtII }
>\header { piece = "Should be page 2"}
> }
>
> Greeting, Ed
--
Dmytro O. Redchuk"Easy to use"
cing slightly.
>
> Lilypond does not remember what it did last time around with that score,
> and it does not throw dice.
Please, I think it would be great it you added your opinion to tracker. I've
marked this issue as "needs-evidence" -- but this "
code in order to reach something
> like the following (but never managed to meet all 4 demands):
>
> if XML: bli (non-empty!) AND
> bla --> LilyPond: title = bli; subtitle = bla
>
> How can I say this in python?
I've added this as 1913:
http://code.google.com/p/lilypond/is
space #40
> }
> }
> }
> }
>
>
> <<<<< end snippet
Could you please prepare a tiny example?
http://lilypond.org/doc/v2.15/Documentation/web/tiny-examples
It could help a lot.
Thank you
On Thu 22 Sep 2011, 09:30 m...@apollinemike.com wrote:
> Is this a regression?
2.12.3 engraves the same output.
> If so, do you know what the last version was that made the two lines equal?
--
Dmytro O. Redchuk"Easy to use" is easy to
open eps
> files in Lilydev so all regtest archives from
> http://lilypond.org/download/binaries/test-output/ are useless for
> me...
It looks like an issue to be reported,
but please, could you be more specific?
What is mensural-ligatures.ly, where could I find it? -- etc.
Thank
912:
http://code.google.com/p/lilypond/issues/detail?id=1912
> \version "2.15.8"
> \score {
> \relative c'' {
>\repeat unfold 6 { a4 a a a }
> }
> }
>
> \score {
> \relative c'' {
>\repeat unfold 6 { c4 c c c }
>
anaVoice \relative c'{
> c d e c
> e d c e
> }
> \layout {
> }
> }
>
>
> With best Wishes
>
> Marek Klein
> http://gregoriana.sk
>
>
> ___
> bug-lilypond mailing list
> bug-li
ank you, added as 1911:
http://code.google.com/p/lilypond/issues/detail?id=1911
As far as I can see from the discussion, it "Needs-evidence"?
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad
t;
> GNU LilyPond 2.12.3
> Processing `bug.ly'
> Parsing...
> Interpreting music...
> bug.ly:15:16: warning: cannot find Voice `vSoprano'
>
> \new Lyrics
> \lyricsto "vSoprano" { \verseTwo
out a day on it), I
> decided to report this before I forget again.
Added as 1875:
http://code.google.com/p/lilypond/issues/detail?id=1875
Please, how critical it is?
Thanks!
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad
On Mon 05 Sep 2011, 10:02 Reinhold Kainhofer wrote:
> Am Monday, 5. September 2011, 09:41:58 schrieb Dmytro O. Redchuk:
> > On Thu 01 Sep 2011, 16:06 Reinhold Kainhofer wrote:
> > > BTW, this is a really minimal example:
> > > \version "2.15.9"
> >
oment as the
> \tempo
> change. In that case, the tempo mark should be reparented to the barline...
Neil mentioned issue 1276. What do you think, should this one be a separate
issue?
Thank you.
--
Dmytro O. Redchuk"Easy to use" is easy t
ond/issues/list?can=7
I am not sure this is bad.
What do you think?
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On Wed 31 Aug 2011, 17:07 Reinhold Kainhofer wrote:
> Am Mittwoch, 31. August 2011, 16:56:10 schrieb Dmytro O. Redchuk:
> > On Sat 13 Aug 2011, 14:56 lilyp...@googlecode.com wrote:
> > > Updates:
> > > Labels: fixed_2_15_9
> >
> > I can not change it to &
nt - change
> breve vertical lines
> http://code.google.com/p/lilypond/issues/detail?id=1767
>
> (No comment was entered for this change.)
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad
this
issue. I am in doubt. _Performance_? -- not sure. Anything else? What?-)
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e aren't any error messages. When you
> fake an older version number everything works out and a new file (with
> content) is created.
Thank you, added as 1825:
http://code.google.com/p/lilypond/issues/detail?id=1825
--
Dmytro O. Redchuk&qu
on.
%--8<--
If it is related to the topic -- it should be corrected to mention
\quoteDuring also, shouldn't it?
If not -- another warning should be added.
Please, let me know. Thanks!
--
Dmytro O. Redchuk"Easy to use
On Mon 15 Aug 2011, 14:03 Reinhold Kainhofer wrote:
> Am Monday, 15. August 2011, 13:22:33 schrieb Dmytro O. Redchuk:
> > On Sun 14 Aug 2011, 22:22 Reinhold Kainhofer wrote:
> > > If one uses landscape setting, i.e.
> > > #(set-global-page-size "a4" 'lan
m to top). The PDF file has the
> proper rotation.
Should 413 be reopened? Or rather "reincarnated"?
http://code.google.com/p/lilypond/issues/detail?id=413
Thank you!
--
Dmytro O. Redchuk"Easy to use" is eas
gt; \markuplines {
> \justified-lines { a a a a a a a a a a a a }
> "a" }
> %%
>
> I think this would be avoided if multi-rows commands were really creating a
> new markup for each line instead of making a single markup.
> A fix for this may probab
ing pattern for 3/4 to be 6
> >beamed quavers, so the implication is that any available quavers
> >are beamed. Gotta say that seems wrong to me, but can we wait
> >until a beaming guru comments before raising this as an issue?
> >
> >--
> >Phil Holmes
> &g
.
>,(+ (cdr $offsets) (cdr (cadddr
> (ly:phrasingslur::calc-control-points grob))
> #})
>
> \relative c'' {
> \time 3/4
> \slurDashed
> c16\(( d) e f g8\) c,8 d16\(( c) b a\)
> \offsetPhrasingSlurPos #'(0.3 . 0) c16\(( d
On Thu 21 Jul 2011, 13:43 m...@apollinemike.com wrote:
> On Jul 21, 2011, at 1:37 PM, Dmytro O. Redchuk wrote:
>
> > On Thu 21 Jul 2011, 13:20 m...@apollinemike.com wrote:
> >> \new Voice
> >> \with { \remove "Rest_engraver" \consists "Completion_r
On Thu 21 Jul 2011, 13:20 m...@apollinemike.com wrote:
> \new Voice
> \with { \remove "Rest_engraver" \consists "Completion_rest_engraver" }
> { r1*6/4 r2 }
>
> This gets me the attached output.
Please, what's the expected output?
--
Dmytro O. Redchuk
that keeping just the slur scoring and an hypothetic
> slur_collision_engraver would do the job?
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
__
ally needed? Can this issue be demonstrated with single
> pitches/chords only? Is \shoftOff necessary to demonstrate the problem?
> Please, this guide can help you: http://lilypond.org/tiny-examples.html )
>
> Thanks!
--
Dmytro O. Redchuk"Easy to use"
> Ties should take noteheads from other contexts into account.
Please send us a tiny example.
(Is three voices really needed? Can this issue be demonstrated with single
pitches/chords only? Is \shoftOff necessary to demonstrate the problem?
Please, this guide can help you: http://lilypond.org/
> because definitions.ily is not in the directory tree
Thank you, I've added this as 1769:
http://code.google.com/p/lilypond/issues/detail?id=1769
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad
ethod for #< map (0)> in
> call (map # #f)
>
> without \displayLilyMusic it works.
I've added this as 1764:
http://code.google.com/p/lilypond/issues/detail?id=1764
Thank you!
--
Dmytro O. Redchuk"Easy to use" is
es, won't we?
So, I think, we should save some energy for that discussion ,)
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
bug-lil
make every commit build the
> baseline, I've done a rebase that includes both commits.
>
> New commit is
>
> ebdea7566554c26f752de6c2bef25df47ec3ee42
Thank you Reinhold and Carl!
Still waiting to verify this in 2.14.2 :-)
--
Dmytro O. Redchuk&qu
as duplicates.
Please, any thoughts?
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
--Jeff Garbers
___
bug-lilypond mailin
etition
"The chord repetition symbol always remembers the last instance of a chord so
it is possible to repeat the most recent chord even if other non-chorded notes
or rests have been added since."
I am not sure, thought. Please, don't mind. I
ion-suggestions
Thank you!
> I see now that the docs only say to call set-accidental-style right in the
> beginning of Staff << ... >>, which I didn't follow. But you, Neil, shows that
> it does work elsewhere.
--
Dmytro O. Redchuk
Bug Squad
___
r
> #1619, for all I know.)
Now there is 1702, "Unaesthetic beam slope", which reflects this situation, I
believe:
http://code.google.com/p/lilypond/issues/detail?id=1702
I mean that including into your code this \override
\override StaffGrouper #'staff-staff-spacing #'
>
> \version "2.13.57"
> \book {
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } { a } { a } >> }
> \score { << { a } {
the behaviour is the same.
> When compiled with 2.13.49, the amount of whitespace after the barline is
> generally smaller, but still isn't corrected for accidental.
Sorry for somewhat late reply (this message have been flagged in my mailbox
since Mon 14 Feb 2011) -
/p/lilypond/issues/detail?id=1747
I've modified your example a bit -- please, take a look and correct me, if I
am wrong .)
Thank you!
--
Dmytro O. Redchuk
Bug Squad
"Easy to use" is easy to say.
change, quite possibly we need all distribution maintainers to
> update/change their build scripts. Is this intentional? Can
> this be reverted? Do we need to warn package maintainers (how?).
I've added this as 1746:
http://code.google.com/p/lilypond/issues/deta
umber directly on the beam . . .
> >
> > I hope that in some way this is useful :)
> I've added this as 1745:
> http://code.google.com/p/lilypond/issues/detail?id=1745
For the record -- tuplet number placement is a subject of issue 696:
http://code.google.com/p/lilypond/issues/d
r release, as is. It distills the problem a little more -- at
> the expense of centering the number directly on the beam . . .
>
> I hope that in some way this is useful :)
I've added this as 1745:
http://code.google.com/p/lilypond/issues/detail?id=1745
Thank you!
--
easier
> than redefining the voice specific fingeringOrientations.
>
> can this be taken as a feature/enhancement request?
I've added 1744:
http://code.google.com/p/lilypond/issues/detail?id=1744
Now issue 153 already _is_ an enhancement request. May be, it appears invalid
after some (m
tly this way?
NR says:
% -8<--
This function is called as follows:
\new Staff <<
#(set-accidental-style 'voice)
{ … }
>>
The accidental style applies to the current Staff by default [...]
% -8<-------
ings = #custom-tuning
> \notes
> }
> >>
> }
>
>
>
>
> ___
> bug-lilypond mailing li
On Mon 04 Jul 2011, 14:17 -Eluze wrote:
> Dmytro O. Redchuk-2 wrote:
> >
> > pps. Let's continue with "\once \set" issue.
> >
> sure - i'll try to summarize:
>
>
> \set deals with context properties
> \override deals with grob propert
".
rem
rem --8<--
I've added it to my fork and will ask Graham to pull it in some future,
I guess.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
lypond -dinclude-settings=- --png %LY%
imconvert %LY%.png -trim %LY%-trim.png
rem 8<--
Note, you need to copy/rename convert.exe to something like imconvert.exe
because windows already has convert.exe in the path.
--
Dmytro O. Redchuk
the same applies to
> multi-system snippets. :)
Anyway, I'll add your suggestion to comments in the script (win version) -- it
can be useful for those who can not (does not want to) install IM.
Thank you!
--
Dmytro O. Redchuk
Bug Squad
On Mon 04 Jul 2011, 14:48 Neil Puttock wrote:
> On 4 July 2011 14:17, Dmytro O. Redchuk wrote:
>
> > I've not tested! I have no any windows (with lilypond and ImageMagick)
> > about.
>
> You don't need ImageMagick. The eps backend will produce a trimmed
sted! I have no any windows (with lilypond and ImageMagick) about.
> Anyway, I'll make up a patch at the office today, Dmytro.
Thank you!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
, added as 1734:
http://code.google.com/p/lilypond/issues/detail?id=1734
ps. I tagged this as Critical. May be this is too high (because of incorrect
syntax?); anyway, I've decided it would be right.
pps. Let's continue with "\once \set" issue.
--
Dmytro O. Redchuk
Bug Squad
can be valid issue (to
change this behavior), but I feel like similar discussions already have been;
I need some time to search, I guess.
Let's wait some time (while I'm searching,) for possible feedback from
developers.
--
Dmytro O. Redchuk
Bug Squad
_
ributor/adding-issues-to-the-tracker
The script is here now:
https://raw.github.com/gperciva/lilypond-extra/master/bug-squad/trimtagline.sh
Thanks!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu
lose.
>
> I'm aware of \override TieColumn #'tie-configuration but would just as soon
> avoid it if possible.
I found this is an instance of known issue, 1126:
http://code.google.com/p/lilypond/issues/detail?id=1126
I have added your example there thougth.
Thank you!
--
e!
As far as I can see, "\once \set" actually does "\set and then \unset". Very
probably this is exactly what it should to do.
So, this is rather an issue and should be documented?
I would add this to this, at the very bottom:
http://lilypond.org/doc/v2.14/Doc
ot; -I
> "/home/fede/lilypond-master/input/regression" -I
> "/home/fede/lilypond-master/Documentation/included" -I
> "/home/fede/lilypond-master/build/mf/out" -I
> "/home/fede/lilypond-master/build/mf/out" -I
> "/home/fed
089 .
>
> %% DynamicTextSpanner collides with DynamicText if the notes are close
> %% to each other.
> %%
Thank you, added as 1725:
http://code.google.com/p/lilypond/issues/detail?id=1725
> \relative c' {
> c4..\p c16\cresc c4..\f c16\cresc
> c1\ff
>
t; Cheers,
> Xavier
>
> --
> Xavier Scheuer
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
t;
>
> I struggled to find a coherent documentation policy/instruction for this
> (although I don't deal with translations).
>
> I don't think having a tracker open is a bad thing, and I'm happy to help
> pushing or editing the CG f
7;ll probably try it in
> 2.18, so if there's some incompatibility, it would be good to
> start working on that now.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On Mon 27 Jun 2011, 19:40 "Jérôme M. Berger" wrote:
> Dmytro O. Redchuk wrote:
> > So, it is *not* your pdf viewer.
> >
> > Wich version do you use? -- I mean binary install or built from sources?
> >
> Binary install. The package descripti
On Mon 27 Jun 2011, 19:24 "Jérôme M. Berger" wrote:
> Dmytro O. Redchuk wrote:
> > On Sat 25 Jun 2011, 08:31 Jérôme M. Berger wrote:
> >> Hi,
> >>
> >> With lilypond 2.14.1, full notes and half notes are drawn filled. For
> >> exa
hing* about ancient music, i can not be sure that my exercises
will produce valid tiny example.
Sorry, we should accept tiny examples only.
Thank you for your effort and contribution!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing lis
- execute_command 1, ("mpost", "-mem=mf2pt1", "-progname=mpost",
> + execute_command 1, ("mpost", "-mem=../../mf2pt1", "-progname=mpost",
>
> Obviously this isn't a proper fix, but it allowed lilypond to compile and run.
>
4.1
>
> ==> uname -a
> Linux wraith 2.6.39-ARCH #1 SMP PREEMPT Mon Jun 6 22:37:55 CEST 2011 x86_64
> AMD
> Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux
>
> Jerome
--
Dmytro O. Redchuk
Bug Squad
_
cker.
If ly file does contain tagline -- it either should not be overriden
("fortunately enough" that script can not override existing tagline)
or should be removed (for a particular test.ly, let's say).
--
Dmytro O. Redchuk
Bug Squad
_
owever, isn't it?
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e need more options? For trimming "in place" or something else?
>
> Cheers,
> - Graham
On Wed 22 Jun 2011, 13:17 David Kastrup wrote:
> lilypond -dinclude-settings=<(echo "\header { tagline = ##f }") --png bug.ly
I does not work here; i don't know why.
On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
> On Tue, Jun 21, 2011 at 12:52:01PM +0300, Dmytro O. Redchuk wrote:
> > In such cases I add
> > \header { tagline = "" }
> > to a source file and then:
> >
> > lilypond --png test.ly
> > co
c1 f c f c f2 d:m a1:7 d:m
> a:7 d:m c f a:7 d:m a:7 d:m }
[...]
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
d~ d~ d) d~( d~ d~ d)
>c~( c~ c~ c) c~( c2 d~ d cis d1)
>cis( d e f) e( d cis d)
> } >>
>}
> >>
>
> Here is the result: uh, no it isn't. What is the preferred method for
> generating a two-system
png >kelbl2.png
>
> (first cutting off the foot line, then cropping down), resulting in
Wow.
In such cases I add
\header { tagline = "" }
to a source file and then:
lilypond --png test.ly
convert test.png -trim test-trim.png
It is ok to me usually.
--
Dm
<<
> { bes='4 f8 f16( f-.) bes4 f8 f16( f-.) | }
> \\
> { d='8 d4 d16 r d8 d4 d16 r | }
> \\
> { d='8 d16 f s4 d8 d16 f s4 | }
> >>
> \break
> bes4 r2. |
> }
>
> ___
> b
it lost -- bug? Or not?
Federico: Well, i've flagged this thread; let's wait a bit.
Thanks!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
{ \Staff
> \remove "Staff_performer"
> }
> \context
> { \Voice
> \consists "Staff_performer"
> }
> }
> } % scor
a tiny example, THANKS!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
> \new TabStaff { \clef "moderntab" \music }
> >>
Thank you, added as 1660:
http://code.google.com/p/lilypond/issues/detail?id=1660
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
> I would write as in the attached file (see diff).
What is wrong there?
What is the problem?
Which issue "Summary" would you propose?
Thank you!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
h
1 - 100 of 284 matches
Mail list logo
