Re: autoBeaming and \set measurePosition

2015-08-20 Thread Phil Holmes 
"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 scenario. Just ignore it?

Yours, Simon







Simon,

What are you trying to do with this example?

Also, for trivially small examples (like this is) I think most people find 
it far easier to comment if you post the code in line, rather than as an 
attachment.  I certainly do.


--
Phil Holmes



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: autoBeaming and \set measurePosition

2015-08-20 Thread Kevin Barry 
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 broken. It's odd for sure, but perhaps
understandable: you're effectively telling LilyPond that a 2/4 bar has
3 beats left, or that a 3/4 bar has 4 beats left. I'm not sure if I
would consider it a bug or not, but it's definitely undesirable.

Kevin

On Thu, Aug 20, 2015 at 8:41 AM, Phil Holmes  wrote:
> "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 scenario. Just ignore it?
>>
>> Yours, Simon
>
>
>
>
> 
>
>
> Simon,
>
> What are you trying to do with this example?
>
> Also, for trivially small examples (like this is) I think most people find
> it far easier to comment if you post the code in line, rather than as an
> attachment.  I certainly do.
>
> --
> Phil Holmes
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: autoBeaming and \set measurePosition

2015-08-20 Thread David Kastrup 
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?
>
> Yours, Simon
>
> \version "2.19.23"
>
> \relative c'{
>   \time 2/4
>   d8 e f g |
>   \set Timing.measurePosition = #(ly:make-moment 3/4)
>   f4
> }

You are setting the measurePosition to a value beyond any valid one.
What are you even trying to achieve here, and why are you not using
\partial instead (which makes sure to set measurePosition at a "safe"
time, after all position-related processing has finished)?

"Doesn’t seem like this is going to appear in any realistic scenario."
is misstating the situation.  This is not about being realistic or not,
this is about being complete nonsense.  I can't even imagine what you'd
expect LilyPond to be doing here.

-- 
David Kastrup

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: autoBeaming and \set measurePosition

2015-08-20 Thread David Kastrup 
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 beam
> before the override is broken. It's odd for sure, but perhaps
> understandable: you're effectively telling LilyPond that a 2/4 bar has
> 3 beats left,

No, he is telling LilyPond that of a 2/4 bar, 3 beats have already
passed regularly and LilyPond forgot to start the next bar in time.

Then he complains that LilyPond does not react to this slander in the
way he expected.

-- 
David Kastrup

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: autoBeaming and \set measurePosition

2015-08-20 Thread Trevor Daniels 

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 scenario. Just ignore it?

Automatic beams which are created using beamExceptions are
triggered when the beam end points are passed.  Skipping the
end point like this means beam creation is not triggered.

I think just ignore it.  If anyone wants to do this it's easy to add a manual
beam.

Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

*.eps and *.svg .gitignore patterns match files in repo

2015-08-20 Thread markdblackwell 
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 matching files be removed?

* Should the top-level .gitignore include a negating pattern, to cause Git
to version-control the files? Such as (in the present case):

* (If the present, peculiar situation is exactly what is desired then)
should the top level .gitignore include some comment explaining it?

Actually, the following files match patterns in the .gitignore's:




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/eps-and-svg-gitignore-patterns-match-files-in-repo-tp179828.html
Sent from the Bugs mailing list archive at Nabble.com.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: *.eps and *.svg .gitignore patterns match files in repo

2015-08-20 Thread markdblackwell 
> 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 context: 
http://lilypond.1069038.n5.nabble.com/eps-and-svg-gitignore-patterns-match-files-in-repo-tp179828p179834.html
Sent from the Bugs mailing list archive at Nabble.com.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Hairpin flared + circled-tip won't work together.

2015-08-20 Thread Karim Haddad 
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 :
>>
>> \version "2.19.25"
>>
>> {
>> \override Hairpin.stencil = #flared-hairpin
>> \override Hairpin #'circled-tip = ##t
>>
>> c'4 \< c'2 c'4 \!
>> |
>> \revert Hairpin.stencil
>> c'4 \< c'2 c'4 \!
>> |
>>
>> }
>>
>> if flared-hairpin and circled-tip are used together, the circled-tip
>> won't
>> appear. It is also the case in the stable version 2.18
>>
>>
> I worked on this a time.  The attached is where I left off.  Note that
> this
> will make circled tips and it will also break Ferneyhough haipins across
> lines (not covered by issue 3357).  I think I put aside working on this
> because of deciding how to deal with breaks in some of the more strange
> shapes possible -- though it shouldn't be too hard to filter this down to
> a
> patch for the tracker issue and leave breaks for later.
>
> Anyway, hope this helps!
>
> David
>


karim.had...@ircam.fr


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Minor glitch in documentation of destination of Windows installation

2015-08-20 Thread Michael Gerdau 
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.de
 GPG-keys available on request or at public keyserver

signature.asc
Description: This is a digitally signed message part.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

lilypond does not compile: fontforge version not detected

2015-08-20 Thread Miroslav Šulc 
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-dir

WARNING: Please consider installing optional programs or files:  dblatex 
pdflatex epsf.tex lh CTAN package (texlive-lang-cyrillic or texlive-texmf-
fonts)

ERROR: Please install required programs:  /usr/bin/fontforge >= 20110222 
(installed: 99da6faa1ea3b4f80ecd333f596ea7dab205325)

See INSTALL.txt for more information on how to build LilyPond
...

here is the output of fontforge:

# fontforge --version
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later 

 with many parts BSD . Please read 
LICENSE.
 Based on sources from 10:14 CEST 19-Aug-2015-ML-D.
 Based on source from git with hash: 
99da6faa1ea3b4f80ecd333f596ea7dab205325e
no xdefs_filename!
TESTING: getPixmapDir:/usr/share/fontforge/pixmaps
TESTING: getShareDir:/usr/share/fontforge
TESTING: GResourceProgramDir:/usr/bin
trying default theme:/usr/share/fontforge/pixmaps/resources
fontforge 10:14 CEST 19-Aug-2015
libfontforge 20150819


it apparently catches git hash instead of the date version.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

\partCombine problem with spanners

2015-08-20 Thread Miguel Jesus 
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 }
}

Thanks,Miguel
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

build/ .gitignore pattern matches files in repo

2015-08-20 Thread markdblackwell 
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 changes to those files. Therefore:

* Should the pattern be changed to /build/ , so it doesn't match the files?

* Should the matching files be removed?

* Should the .gitignore pattern be deleted?

* (If the present, peculiar situation is exactly what is desired, then)
should the top level .gitignore include some comment explaining it?

The following files match the pattern in the top-level .gitignore:





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/build-gitignore-pattern-matches-files-in-repo-tp179867.html
Sent from the Bugs mailing list archive at Nabble.com.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond