Currently, the top level .gitignore (of LilyPond's repository) contains this
pattern:
I found no pattern negating this, in any .gitignore file (at any directory
level).
Currently, the repository on the server contains files (see below) which
match this pattern.
Because of this, Git will ignore c
2nd note should be marked "Solo". Instead, both the note and the full measure
rest appear.Do you think this might be related to issues 4095 and 4454?
\version "2.19.25"
one = \relative c' { c1\< | f\mf }
two = \relative c' { c1\< | R\! | }
\score {
\new Staff { \partcombine \one \two }
i attempted to install lilypond- gentoo ebuild but it fails because it
does not detect fontforge version correctly:
# ./configure
...
configure: creating ./config.status
config.status: creating config.make
config.status: creating config.hh
configure: WARNING: unrecognized options: --with-ncsb
Dear bug squad,
in Documentation/web/download.texi, line 486 it reads LilyPond will
be installed under "C:\Program Files" on Windows. Since most current
Windows Versions are 64bit this probably should read
"C:\Program Files (x86)".
Kind regards,
Michael
--
Michael Gerdau email: m...@qata.
Thanx a lot David!
This is great !
Best
K
> Hi Karim,
>
> On Wed, Aug 19, 2015 at 11:01 AM, Karim Haddad
> wrote:
>
>> Hello list,
>>
>> I hope this issue is not reported. If it is sorry to post it again :
>>
>
> https://code.google.com/p/lilypond/issues/detail?id=3357
>
>
>>
>> in this example :
> Actually, the following files match patterns in the .gitignore's
Currently, the repository on the server contains those *.eps and *.svg
files. (I neglected to state this, clearly.)
Because of patterns in the .gitignore's, Git will ignore changes to those
files.
--
View this message in contex
Currently, the top level .gitignore (of LilyPond's repository) contains these
patterns:
I found no pattern negating them, in any .gitignore file (at any directory
level).
If any files match patterns in the .gitignore's, then:
* Should those .gitignore patterns be deleted?
* Should those matchin
Simon Albrecht wrote Thursday, August 20, 2015 1:11 AM
> I don’t quite know what I’m supposed to think of this: With 3/4, there
> is no beam between the third and fourth quavers. It doesn’t happen with
> -1/4, 0, 1/4, or 2/4. Doesn’t seem like this is going to appear in any
> realistic scenari
Kevin Barry writes:
> Tinkering with your example seems to suggest that any value that is
> larger than the time signature will produce the unwanted behaviour.
>
> That is, if you set the Timing.measurePosition to anything bigger than
> the normal size of a bar in the current time signature, the
Simon Albrecht writes:
> Hello,
>
> I don’t quite know what I’m supposed to think of this: With 3/4, there
> is no beam between the third and fourth quavers. It doesn’t happen
> with -1/4, 0, 1/4, or 2/4. Doesn’t seem like this is going to appear
> in any realistic scenario. Just ignore it?
>
> Y
Tinkering with your example seems to suggest that any value that is
larger than the time signature will produce the unwanted behaviour.
That is, if you set the Timing.measurePosition to anything bigger than
the normal size of a bar in the current time signature, the beam
before the override is bro
"Simon Albrecht" wrote in message
news:55d51b39.2010...@mail.de...
I don’t quite know what I’m supposed to think of this: With 3/4, there
is no beam between the third and fourth quavers. It doesn’t happen with
-1/4, 0, 1/4, or 2/4. Doesn’t seem like this is going to appear in any
realistic scena
12 matches
Mail list logo