%% When using \parenthesize on whole bar or multi measure rests, no
parentheses
%% will be printed:
\version 2.14.2
\paper { ragged-right=##t }
\parenthesize R1
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Hello everybody,
in the following example, I would very much like the f arranged to the
right of the g. I have tried several solutions, but none worked, and
also I think that it ought to work without an \override command. Can
anyone think of a solution?
Thanks, Simon
Here’s the code:
Hello,
when working on a score a few days ago I noticed that I would prefer
(and have often seen in printed scores) the staves on the first page (if
they are fewer than normal due to headers) to be stacked at the bottom
of the page with normal distances rather than have them spread over the
in this case (or split
the rest automatically?).
Best regards,
Simon Albrecht
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
,
Simon Albrecht
attachment: clef misplaced.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Am 19.09.2013 11:04, schrieb Phil Holmes:
Simon Albrecht simon.albre...@mail.de wrote in message
news:523a27fb.8020...@mail.de...
Hello Lilypond community,
in a recent project I encountered the following bug:
If a clef change occurs at an invisible barline, then in certain cases
the clef
Hello Lilypond community,
in a recent project I encountered the following bug:
If a clef change occurs at an invisible barline, then in certain cases
the clef will be printed far away from its actual position. Minimal
example:
I don't understand why the invisible barline is there. What's the
Help!
Maybe this is another time I just overlook the crucial tiny mistake in
my code, but to me, it seems that removeWithTag fails in the following
example (that is, all the tagged notes are printed), and only if there
is a note between the \removeWithTag and \tag commands.
\relative {
I tried ly 2.17.24 and 2.16.2 with identical results.
Am 13.10.2013 00:58, schrieb Simon Albrecht:
Help!
Maybe this is another time I just overlook the crucial tiny mistake in
my code, but to me, it seems that removeWithTag fails in the following
example (that is, all the tagged notes
probably being the adequate value] as a first entry for the
definition of AccidentalSuggestion in define-grobs.scm .
Let me know if you need any examples of this.
Best regards
Simon Albrecht
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
Hello,
Am 15.12.2013 12:01, schrieb James:
Simon
On 12/12/13 22:17, Simon Albrecht wrote:
Hello,
if both an AccidentalSuggestion and a slur are attached to a note,
LilyPond places both as expected, but issues a warning about
avoid-slur not being defined for AccidentalSuggestion
.
(almost) Minimal example:
\version 2.18.0
\language deutsch
\paper {
#(set-paper-size a7 'landscape)
}
\relative { g'2 f
{ \voiceTwo e d c }
\new Voice = B I { \voiceOne g' f e }
\new Lyrics \lyricsto B I \lyricmode { What a mess! }
\oneVoice
c d e
}
--
Simon Albrecht
@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Simon Albrecht, Kirchenmusikstudent
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hello,
lenghty \marks which are at the beginning of a line tend to run into the
margin or even out of the page. It would be nice to make the
center-alignment more flexible and move the mark so that it stays inside
the actual line. Minimal example attached.
Best regards
--
Simon Albrecht
.
The question is whether there is something in the docs that would have
contributed to a misunderstanding, or whether there could have been
something in the docs that would have prevented it.
--
Simon Albrecht, Kirchenmusikstudent
___
bug-lilypond mailing list
Hello everybody, hello Pierre,
(is there a specific way to submit LSR bugs?)
The version of snippet No. 445 http://lsr.di.unimi.it/LSR/Item?id=445
currently in the repo doesn't work correctly since 2.16.0 due to
NoteEvents not being wrapped in EventChord anymore. I attach an updated
version:
Hello,
issue 2753 http://code.google.com/p/lilypond/issues/detail?id=2753 has
been resolved with the recent (or how recent were they?) changes on slur
placement. The 2.19.3 output for the example in the issue is very nice.
Regards,
Simon
___
Hello,
if a slur reaches around a note, they may touch as in the attached
example. There should be some kind of padding there.
Regards,
Simon
\version 2.19.3
\paper { #(set-paper-size a10 'landscape) }
\header { tagline = ##f }
{ e'1 } \\
{ g'2( a') }
slur-padding.pdf
Description:
Am 21.03.2014 14:37, schrieb Phil Holmes:
Simon Albrecht simon.albre...@mail.de wrote in message
news:532b8726.9000...@mail.de...
Hello,
if a slur reaches around a note, they may touch as in the attached
example. There should be some kind of padding there.
Regards,
Simon
For a simple
Am 21.03.2014 18:08, schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
That music looks like it is entered in a bad order. In general, the top
voice should come first. Where it doesn't, you are dealing with an
inversion. In general, one should avoid flipping things like
Hello,
{ c' \tweak font-size #-3 e'1
c'' \tweak font-size #-3 e'' }
produces two chords with two semibreves each, the one normal-sized, the
other smaller. The attached output from 2.19.3 shows that they are
(left-/right-)aligned as if they had stems. This looks ill-balanced, in
my eyes they
Hello Lilyponders.
For annoyance at issue 2010
http://code.google.com/p/lilypond/issues/detail?id=2010 and gratitude
towards the one who solves it, I chip in a university student's moderate
bounty of 25€.
By the way: how is an issue's priority determined? There is no
explanation in the
Am 29.05.2014 09:53, schrieb Urs Liska:
Am 29.05.2014 09:15, schrieb Javier Ruiz-Alma:
I'm typesetting the attached music using four voices. However, a
shifted quarter note refuses to merge with the half-note from other
voice. I suspect it has to do with both having same stem direction,
So sorry, wrong list…
Am 26.06.2014 12:53, schrieb Simon Albrecht:
Am 26.06.2014 09:39, schrieb Pierre Perol-Schneider:
\once \override AccidentalSuggestion #'outside-staff-priority = ##f
\once \override AccidentalSuggestion #'avoid-slur = #'inside
\once \override AccidentalSuggestion #'font
Am 26.06.2014 13:33, schrieb David Kastrup:
And he's right with that as well... Have you actually tried it?
My mistake again. Sorry for being pert and not checking first. I wasn’t
aware that your parser improvements had gone so far…
Best regards,
Simon
Hello Ewen,
may I ask what this has to do with LilyPond?
Especially the bug-lilypond list is only intended for qualified bug
reports concerning LilyPond, and in case there is any hidden relation to
LilyPond in your project, you might eventually have better adressed the
lilypond-u...@gnu.org
Hello,
I currently try out the consequences of issue 3648
http://code.google.com/p/lilypond/issues/detail?id=3648, namely the
possibility to use isolated durations as frequently as has been normal
for isolated pitches. It certainly means a change to the habits of
entering music in LilyPond
Am 08.07.2014 12:36, schrieb James:
On 08/07/14 06:37, Urs Liska wrote:
Am 07.07.2014 23:23, schrieb Federico Bruni:
2014-07-07 21:40 GMT+02:00 Michael Gabor i...@elala.de:
Dear Lilypond-Team,
In LM 2.18.2 german version under 2.7.3 Generalbaß at the end of
the page
is an example on
Hello,
if I include any non-ASCII character into a file name, I get the
following at the end of the log
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28
-dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
-r1200 -sDEVICE=pdfwrite -sOutputFile=./non-áscii.pdf
Hello Justus,
please (re-)read http://lilypond.org/website/bug-reports.de.html
concerning the usage of this mailing list. You may ask every question
you like on lilypond-u...@gnu.org.
Best regards,
Simon
Am 21.07.2014 19:12, schrieb Justus Schümmer:
Hi. Here are two small issues:
1. When
Am 01.08.2014 16:19, schrieb Jos Leussink:
I'm not top posting.
wellcome test file of version 2.18 mentions:
\version 2.16.0
You’ll find many files in the lily distribution which carry an older
version statement, since there was no update (and needn’t have been).
This is surprising at first,
Hello,
as a followup to the ly-user thread on ottavation bracket/fermata
stacking I noticed the following problem:
By default, OttavaBracket has a minimum-length of 1 and the text is
right-aligned to the first note in the range of the ottavation. Thus,
it's sometimes impossible to discern
Hello,
upon reading the list of markup commands in the NR, I noticed several
issues, which I’d like to report. I apologize for not making a patch
myself; firstly, I have been uncertain at some points, secondly others
are more apt at English phrasing, and also I’m not yet familiar with the
Hello,
yesterday I tried out make-dynamic-script and in my first attempt forgot
some :
pDolce = #(make-dynamic-script (markup #:dynamic p #:italic dolce))
Compiling the attached example file results in
fatal error: make-dynamic-markup: Invalid argument in position 1.
Expect: markup, found:
Hello,
in the following section
http://lilypond.org/doc/v2.18/Documentation/usage/common-errors#an-extra-staff-appears
the second example seems to be obsolete, at least with 2.18 both codings
have identical output.
Yours, Simon
___
bug-lilypond
Am 31.08.2014 um 14:42 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Hello,
yesterday I tried out make-dynamic-script and in my first attempt
forgot some :
pDolce = #(make-dynamic-script (markup #:dynamic p #:italic dolce))
Compiling the attached example file results
Am 31.08.2014 um 15:14 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Hello,
in the following section
http://lilypond.org/doc/v2.18/Documentation/usage/common-errors#an-extra-staff-appears
the second example seems to be obsolete, at least with 2.18 both
codings have
Am 31.08.2014 um 22:44 schrieb Peter Van Kranenburg:
Dear list,
If an invisible rest in the top staff is followed by a key change, the
spacing in the other staffs is incorrect.
It’s the other way round: the key change is followed by the invisible
rest. Or the rest follows the key change, if
Am 01.09.2014 um 19:34 schrieb James:
On 31/08/14 13:04, Simon Albrecht wrote:
Hello,
upon reading the list of markup commands in the NR, I noticed several
issues, which I’d like to report. I apologize for not making a patch
myself; firstly, I have been uncertain at some points, secondly
Hello,
following James’ suggestion I now start a series of e-mails concerning
the observations I made on reviewing NR A.11, the list of markup commands.
First issue: Now, \caps and \smallCaps mean just the same in LilyPond. I
find that unusual: normally small caps means that all letters are
Hello,
the second issue I found is that there are one or two commands which
don’t fit into the usual \naming-convention for markup commands: these
are \customTabClef and perhaps also \epsfile. One might argue about the
latter, but it would certainly improve legibility to have \eps-file
Am 06.09.2014 um 15:34 schrieb Dan Eble:
I'm not top posting.
% The part combiner keeps voices separate for crescendi spanning
% different intervals of time, but not for differing absolute
% dynamics. For consistency, I think it should keep the voices
% separate for differing absolute
Looks like it’s worth a bug report and issue tracker, doesn’t it? About
completion heads engraver and addlyrics being incompatible.
However, the attached version of the file using @code{ \new Lyrics
\lyricsto first } instead of @code{ \addlyrics } works as expected for
me*. So working around
hope you don’t mind if I continue to
post some thoughts which come to my mind. I know they are eccentrical
and far from implementation reality sometimes and do not intend but to
propose them to your judgement :-)
Best, Simon
Am 07.09.2014 um 00:23 schrieb James:
On 06/09/14 21:17, Simon
Am 15.09.2014 um 21:41 schrieb Guy Stalnaker:
All,
Sometimes Lilypond changes how it does its Fitting music on ...
calculations when it decides what can fit on a page and what cannot.
In this case, after four pages on which the fitting process puts two
systems per page, the subsequent pages
Am 27.09.2014 um 17:31 schrieb James:
Just curious why it matters, or what is gained if a grob is documented
whether it 'prints' ouput or not, if the actual behaviour of what the
grob does is documented (i.e. in the IR). James
It’s just for easier understanding. In an earlier user list thread,
Hello,
I find the current coding of LSR snippet 265 leaves much room for
improvement, especially by using \set stanza for the braces and the more
convenient commands \left-brace and \right-brace.
Attached is my new version. I hope you like it ;-)
Best, Simon
%%
Hello Malte,
there is an extra mailing list covering translation issues. I put it in CC.
Best regards,
Simon
Am 30.09.2014 um 11:48 schrieb Malte Meyn:
I'm not top posting.
The English documentation writes
“The simple way of setting parenthesis-style arpeggio brackets does not work
for
Am 04.10.2014 um 23:13 schrieb Peter Crighton:
As you can see in the following code and the attached image, there is
a possible bug when using \RemoveEmptyStaves with voices in different
keys (such as in a score with transposing instruments): key signatures
appearing only in hidden empty
Hello Federico,
I’m using this feature on a regular basis now, so I think I can explain
what is meant. For example it is extremely useful for tied notes, since
those have (almost) always the same pitch:
a2~ 1~ 2.
Here it works also if I omit the ties:
a2 1 2. , because the first note has an
Hello everybody,
in the attached example, two tied notes (of the same pitch) in different
bars have their stems placed in different directions by the melody
engraver. This is very confusing, so the engraver should take ties
between notes of the same pitch (that is, as opposed to bis~ c for
Hello,
see https://code.google.com/p/lilypond/issues/detail?id=962 and
https://code.google.com/p/lilypond/issues/detail?id=904.
It is requested in http://lilypond.org/bug-reports.html that you look
such things up in the tracker yourself, as a contribution to improving
workflows in Lilypond.
for tie chord will give you 15 results with two of them
matching your problem.
Best, Simon
--Christopher
On Dec 28, 2014, at 1:56 PM, Simon Albrecht simon.albre...@mail.de wrote:
Hello,
see https://code.google.com/p/lilypond/issues/detail?id=962 and
https://code.google.com/p/lilypond/issues
Hello,
I just found a broken link to the old LSR domain in issue 2368 (with
.dsi. instead of the now valid .di.).
There probably is no convenient way of updating those links, is there?
Yours sincerely,
Simon
___
bug-lilypond mailing list
Am 30.12.2014 21:45, schrieb Thomas Morley:
2014-12-30 21:28 GMT+01:00 David Kastrup d...@gnu.org:
Simon Albrecht simon.albre...@mail.de writes:
Hello,
I just found a broken link to the old LSR domain in issue 2368 (with
.dsi. instead of the now valid .di.).
There probably is no convenient
Hello list,
see the attached code: The hairpins collide, if and only if
-- there is a barline in \n (comment to test)
-- and there is a half note or rest or multi-measure-rest in the other part.
Somewhat obscure and difficult to isolate, but easy to work around.
Yours, Simon
\version 2.19.8
Hello list,
it seems that the \tweak command does not have any effect on multi
measure rests, neither with nor without specifying the grob:
\version 2.19.8
{ \tweak MultiMeasureRest.color #red R1 \tweak color #red R1 }
I couldn't find an entry in the issue tracker, nor any mention of this
Hello,
in many scores of modern music, ties are not drawn to their full extent,
but (speaking in lilypond terms :-)) only as a RepeatTie on the second
chord (example attached), eventually also with a LaissezVibrerTie on the
first chord. This is often necessary because full-length ties would
Am 22.03.2015 um 15:03 schrieb Dan Eble:
Does anyone else think that the automatic placement of the second rest in this
example is distractingly low in the “z” style?
I think it’s right at least in the third bar to not place it any closer
to the note, so I’d support Lily’s behaviour here.
Hello,
in my stylesheets, I usually include
germanTagline = \markup {
\italic
\pad-to-box #'(0 . 0) #'(0 . 3)
{
\with-url #http://lilypond.org/;
\line {
#(format #f Noten gesetzt mit LilyPond ~a ~a www.lilypond.org
(lilypond-version)
(ly:wide-char-utf-8
Am 16.03.2015 um 13:44 schrieb Noeck:
Hi,
I hope you agree that it’s worthwhile to make all these thoughts and
that it would be good to have such functionality in an easy-to-use way.
I do agree very much. It might seem like a minor thing, but I remember
when I used LilyPond for the first
Am 15.03.2015 um 17:18 schrieb Simon Albrecht:
Hello,
in my stylesheets, I usually include
germanTagline = \markup {
\italic
The \italic here is my personal preference, of course. But if the
appearance of the tagline is generated through a dedicated markup
function, it’s most easy to adapt
Thanks for elaborating, Harm. That’s some elegant coding with which I
couldn’t have come up :-)
Am 15.03.2015 um 19:22 schrieb Thomas Morley:
[snip]
\version 2.19.16
%% Please note, \language has to be declared before 'used-language'
%% is done or included, (if stored elsewhere)
\language
Hello Michael,
I think this question is more appropriate for the -user list.
Since I usually call lily from inside frescobaldi, my solution to this
has been defining a variable for the resulting pitch:
\version 2.18
newTonic = des
music = \relative { c' }
\score {
\transpose c \newTonic
Am 16.03.2015 um 17:43 schrieb Michael Schuerig:
On Monday 16 March 2015 11:26:30 David Nalesnik wrote:
Am 16.03.2015 um 15:02 schrieb Michael Schuerig:
I've only been using LilyPond for a rather short time, so far mostly
for engraving short snippets transposed into several keys for
Am 16.03.2015 um 10:22 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Thanks for elaborating, Harm. That’s some elegant coding with which I
couldn’t have come up :-)
Am 15.03.2015 um 19:22 schrieb Thomas Morley:
[snip]
\version 2.19.16
%% Please note, \language has
Am 06.03.2015 um 17:00 schrieb David Kastrup:
Aurélien Bello i...@aurelienbello.com writes:
Dear all,
I would like to inform about an exciting project I made with LilyPond.
Every year, the Berlin Philharmonic Orchestra has its own Eastern
Festival in Baden-Baden. They play one big opera and
Am 06.03.2015 um 16:48 schrieb Aurélien Bello:
Dear all,
I would like to inform about an exciting project I made with LilyPond.
Every year, the Berlin Philharmonic Orchestra has its own Eastern Festival in
Baden-Baden. They play one big opera and numerous symphonic concerts.
This year, the
Weitergeleitete Nachricht
Betreff:Re: Re: Dynamics negative Y-offset
Datum: Fri, 6 Mar 2015 01:45:54 +0100
Von:Thomas Morley thomasmorle...@gmail.com
An: Simon Albrecht simon.albre...@mail.de
Kopie (CC): lilypond-user lilypond-u...@gnu.org, Phil Holmes
m...@philholmes.net
2015-03
Hello Ralph,
you’ll be interested in reading
http://lilypondblog.org/2014/09/how-to-write-readable-tuplets/.
Indeed, the behaviour you describe is intentional in that Lily holds the
user responsible to write sensible tuplet code, since there are
different conventions, not only the one you
Hello Bug Squad,
please open a tracker issue for this thread. I’m going to make another
essay at coding something sensible.
Yours,
Simon
Am 16.03.2015 um 12:13 schrieb Simon Albrecht:
Am 16.03.2015 um 10:22 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Thanks
wrong list to forward to…
Weitergeleitete Nachricht
Betreff: Re: Implementation of \tuplet allow both incorrect and correct
musical expressions
Datum: Thu, 26 Mar 2015 10:53:26 +0100
Von:Simon Albrecht simon.albre...@mail.de
An: Ralph D. Jeffords ralph.d.jeffo
Am 31.03.2015 um 14:59 schrieb Phil Holmes:
Leo Naab leo.n...@gmx.de wrote in message
news:loom.20150331t133343-...@post.gmane.org...
I'm not top posting.
I have a special lilypond file with let's lilypond.exe crash. The
file works
fine with version 2.19.15, but not with 2.19.17.
The crash
Am 05.03.2015 um 12:58 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Hello list,
I use a music function to tweak the X and Y-offsets for a grob. This
function used to work in 2.19.8, but in 2.19.15 and .16 it just
remains without effect – there are no kind of messages
Am 05.03.2015 um 16:53 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Am 05.03.2015 um 12:58 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Hello list,
I use a music function to tweak the X and Y-offsets for a grob. This
function used to work
Well, there’s reason enough to redirect this to bug-lilypond, isn’t it?
Somehow, Mozilla Thunderbird messes up the code examples, so I can’t do
so well. Perhaps the OP’s and Harm’s first mails in the thread,
respectively, should suffice for illustration.
~Simon
Am 03.03.2015 um 23:01 schrieb
Hello list,
I use a music function to tweak the X and Y-offsets for a grob. This
function used to work in 2.19.8, but in 2.19.15 and .16 it just remains
without effect – there are no kind of messages. Any idea where this
might come from?
Best, Simon
% 2.19.8 works, 2.19.15 doesnât
Hello,
if in Lily 2.19.15 NullVoice is \consisted with the Ambitus_engraver,
there are (for one NullVoice) three instances of
programming error: tried to get a translation for something that is no
child of mine
which cause the program to abort. This used to work in v2.19.8. Minimal
Hello,
Patrick reported the problem below on ly-user and I think this is
unintended behaviour deserving a tracker issue. Parts are less common
with vocal music than with instrumental music (since often one has a
vocal score with piano reduction anyway), but not uncommon, so the
problem
Hello,
as Harm has pointed out, the following example gives unexpected (i.e.
different) output:
\version 2.19
repeat-note =
#(define-music-function (parser location music)(ly:music?)
(make-sequential-music (list music (ly:music-deep-copy music
\absolute { c'1 \repeat-note c'' }
Am 25.04.2015 um 13:17 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Hello,
as Harm has pointed out, the following example gives unexpected
(i.e. different) output:
\version 2.19
repeat-note =
#(define-music-function (parser location music)(ly:music?)
(make
Hello,
Completion_heads_engraver doesn’t use dotted breve notes for its output,
where smaller note values work as expected.
Thanks, Simon
\version 2.19.17
#(ly:set-option 'point-and-click #f)
\paper { #(set-paper-size a8 'landscape) indent = 0 }
\header { tagline = ##f }
\new Voice
{
Hello,
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-vocal-music#multiple-syllables-to-one-note
has an example covering the use of LyricTie with Italian text. Using the
same feature with German text (and probably other languages too), or
more accurately, with
Hello James,
Am 07.05.2015 um 09:57 schrieb James:
Simon,
On 06/05/15 18:39, Simon Albrecht wrote:
Am 06.05.2015 um 09:06 schrieb James Lowe:
On 06/05/15 00:01, Simon Albrecht wrote:
Hello,
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-vocal-music#multiple
\bar ||
c'1 \
\time 2/4
c'2 \f
\bar ||
c' \
\key g \major
c' \f
\bar ||
c' \
\key des \major
\time 16/8
c' \f
}
2015-05-06 10:06 GMT+03:00 James Lowe p...@gnu.org:
On 06/05/15 00:01, Simon Albrecht wrote:
Hello,
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-vocal-music
Am 06.05.2015 um 09:06 schrieb James Lowe:
On 06/05/15 00:01, Simon Albrecht wrote:
Hello,
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-vocal-music#multiple-syllables-to-one-note
has an example covering the use of LyricTie with Italian text. Using the
same feature
Well, that seems like a very specific use case. And you may easily work
around using
\version 2.19.17
{
\stopStaff s1 \once\omit Staff.BarLine \break
\startStaff a \stopStaff
}
I agree that one might expect not to have a lonely bar line there, but
it is printed regardless of the break.
Hello,
currently, ambitus are placed at the very beginning of the first system,
before clef and key signature. However, its meaning depends on both:
without a clef, the pitches are unspecified, and it’s confusing that
accidentals are set based on a key which has not yet been ‘announced’
(See
Am 07.04.2015 um 23:43 schrieb Dan Eble:
On Apr 7, 2015, at 00:23 , Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com wrote:
2015-04-07 3:35 GMT+02:00 Dan Eble d...@faithful.be mailto:d...@faithful.be:
% Is this supposed to leave a stem showing?
\version 2.19.17
\hide c''4
Yes, because
Am 20.05.2015 um 08:19 schrieb James Lowe:
On 20/05/15 06:28, Connor Harris wrote:
In Lilypond 2.18.2 and possibly later versions, hairpins that end at the
beginning a measure are engraved with their right ends slightly left of
the barline. This looks bad if the note follows a key change, as
Hello Bug squad,
is the list in
http://lilypond.org/doc/v2.19/Documentation/contributor/bug-squad-checklists
anywhere near up-to-date? It seems we don’t have a really prompt squad
at hand, and I should be able to take over one or two days, except for
Monday and Thursday.
Yours, Simon
Am 04.06.2015 um 09:51 schrieb Phil Holmes:
Simon Albrecht simon.albre...@mail.de wrote in message
news:556f59d4.20...@mail.de...
Hello Bug squad,
is the list in
http://lilypond.org/doc/v2.19/Documentation/contributor/bug-squad-checklists
anywhere near up-to-date? It seems we don’t have
Forwarding to the bug-list.
Yours, Simon
Am 07.06.2015 um 02:52 schrieb Gilberto Agostinho:
Hi all,
I found a little problem with the \accidentalStyle dodecaphonic-no-repeat.
When there is a grace note between two identical pitches, the second one
does not receive an accidental as it's suppose
Hi Nick,
I can’t confirm that on Ubuntu, it compiles just fine. Can you narrow
down the problem and provide a tiny example
http://lilypond.org/website/tiny-examples.html, please?
Thanks, Simon
Am 09.06.2015 um 23:22 schrieb Nick Payne:
On 10/06/2015 07:02, musicus wrote:
Hi Klaus,
\
R1*2\!
}
\score {
\new Staff \partcombine \mus \musTwo
}
On Friday, 19 June 2015, 10:29, Miguel Jesus
miguel.jesus1...@yahoo.com wrote:
Thank you, Simon. Next time I'll have a little more patience before I
report a bug.
On Wednesday, 17 June 2015, 15:46, Simon Albrecht
simon.albre
Just for the record: I forwarded this to ly-devel.
~ Simon
Am 25.06.2015 um 22:14 schrieb Dénes Harmath:
Dear developers,
are there any plans to build a Docker image for building LilyPond? It would
be a much more lightweight solution than a VirtualBox image, so I think
contributors would be
Am 24.06.2015 um 19:39 schrieb Abraham Lee:
Robert,
Doesn't look like you're doing anything wrong. In the code, it doesn't
appear that \bookpart is sensitive to this variable,
Can anyone confirm if this is intended behaviour? I’d agree that we
might expect it to work.
The NR doesn’t specify
Am 18.06.2015 um 17:06 schrieb Gilberto Agostinho:
% strange behaviour when more than 2 notes are repeated
\makeClusters {
\override ClusterSpanner.padding = #'-0.25
c'1
c'
c'
}
The following shows that it’s not a triangle but a trapezium which is drawn:
% strange behaviour when more
Hello Miguel,
Am 17.06.2015 um 14:14 schrieb Miguel Jesus:
I'm having a problem with \partcombine (I'm sorry for the long examples but
this is the code I'm working with right now). With this code the voices
aren't combined properly:
[snip]
At first I thought it had to do with the spacer
Am 13.06.2015 um 20:03 schrieb Thomas Morley:
2015-06-13 19:16 GMT+02:00 Daniel Rosen drose...@gmail.com:
Running LilyPond 2.19.21 on 64-bit Windows 7, I get an odd pop-up error dialog
in a number of different circumstances. Below are two examples.
Example #1 gives a warning in 2.18.2,
1 - 100 of 415 matches
Mail list logo
