Updates:
Labels: Patch-new
Comment #27 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c27
Fixes NoteColumn vs SpanBar collisions.
http://codereview.appspot.com/5323062
___
Pavel Roskin writes:
> On Fri, 11 Nov 2011 23:21:42 +0100 (CET)
> Werner LEMBERG wrote:
>
>>
>> > f♯ is shorter and more readable than fsharp, let alone fis.
>>
>> In Germany and Austria, f♯ is *never* used. Only fis and nothing
>> else.
>
> I'm sure the signs for accidentals are used in the
Comment #7 on issue 2032 by k-ohara5...@oco.net: Patch: Fold
set-time-signature into \time
http://code.google.com/p/lilypond/issues/detail?id=2032
The regression test is showing intermittent behavior due to issue 1723,
nothing to do with the patch in question.
This one test will probably
Quoting Carl Sorensen :
I think the point Werner was making is that accidentals are used on a
staff. The graphical representation of f sharp is a notehead on the f
line or space (depending on which staff, and which octave) with a sharp
symbol either before the note (an accidental) or in the key
Updates:
Status: Started
Labels: -Patch-new Patch-review
Comment #6 on issue 2032 by pkx1...@gmail.com: Patch: Fold
set-time-signature into \time
http://code.google.com/p/lilypond/issues/detail?id=2032
Passes make and one reg test showed up
Attached
James
Attachments:
Updates:
Cc: -hanw...@gmail.com
Comment #9 on issue 1686 by hanw...@gmail.com: Compile scheme files to
scm/out when using Guile V2.n. Also load and run .go files if available
http://code.google.com/p/lilypond/issues/detail?id=1686
(No comment was entered for this change.)
_
Hello,
2011/11/12 Paul Scott :
..
>> The text representation of f sharp in germany and austria is fis. When
>> you want to describe a note in text, that's how you do it. In english, we
>> write "f sharp";
>
> In a book probably. In an email F#.
Based on that answer, how do _you_ write 'b flat'
On 11/11/2011 04:31 PM, Carl Sorensen wrote:
>
> On 11/11/11 4:49 PM, "Pavel Roskin" wrote:
>
>> On Fri, 11 Nov 2011 23:21:42 +0100 (CET)
>> Werner LEMBERG wrote:
>>
f♯ is shorter and more readable than fsharp, let alone fis.
>>> In Germany and Austria, f♯ is *never* used. Only fis and noth
Issue 2025: Make safe utility available via new (scm safe-utility-defs)
scheme module.
http://code.google.com/p/lilypond/issues/detail?id=2025
This issue is no longer blocking issue 1686.
See http://code.google.com/p/lilypond/issues/detail?id=1686
--
You received this message because you are li
Updates:
Blockedon: -2025
Comment #8 on issue 1686 by ianhuli...@gmail.com: Compile scheme files to
scm/out when using Guile V2.n. Also load and run .go files if available
http://code.google.com/p/lilypond/issues/detail?id=1686
(No comment was entered for this change.)
Updates:
Status: Fixed
Labels: -Patch-push
Comment #9 on issue 2025 by ianhuli...@gmail.com: Make safe utility
available via new (scm safe-utility-defs) scheme module.
http://code.google.com/p/lilypond/issues/detail?id=2025
Pushed as be9de62..1c8ae9f
Ian
___
On 11/11/11 4:49 PM, "Pavel Roskin" wrote:
>On Fri, 11 Nov 2011 23:21:42 +0100 (CET)
>Werner LEMBERG wrote:
>
>>
>> > f♯ is shorter and more readable than fsharp, let alone fis.
>>
>> In Germany and Austria, f♯ is *never* used. Only fis and nothing
>> else.
>
>I'm sure the signs for acciden
>> > f♯ is shorter and more readable than fsharp, let alone fis.
>>
>> In Germany and Austria, f♯ is *never* used. Only fis and nothing
>> else.
>
> [...]
>
> Using those signs in a text file would be a new thing. Maybe
> accidentals should be written before the notes, as in the score
> (♯f), bu
On Fri, 11 Nov 2011 23:21:42 +0100 (CET)
Werner LEMBERG wrote:
>
> > f♯ is shorter and more readable than fsharp, let alone fis.
>
> In Germany and Austria, f♯ is *never* used. Only fis and nothing
> else.
I'm sure the signs for accidentals are used in the musical scores, even
in Germany :)
> f♯ is shorter and more readable than fsharp, let alone fis.
In Germany and Austria, f♯ is *never* used. Only fis and nothing
else.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hello!
It's not exactly a bug, more like a feature request :)
I have noticed that convert-ly removes the \encoding and converts
everything to UTF-8. So I hoped I could use some Unicode symbols to
make the sources more compact and readable:
\version "2.14.2"
\score {
\new Staff { d♭8 f♯ }
\l
Updates:
Labels: -Patch-needs_work Patch-new
Comment #5 on issue 2033 by d...@gnu.org: Patch: This removes ly:export for
real and separates read/eval for Scheme expressions.
http://code.google.com/p/lilypond/issues/detail?id=2033
Since patch removes source files, you need to remake th
Comment #5 on issue 2032 by d...@gnu.org: Patch: Fold set-time-signature
into \time
http://code.google.com/p/lilypond/issues/detail?id=2032
Testing would be welcome, and you need to set PATCH_LEVEL in VERSION to 19.
___
bug-lilypond mailing list
b
Updates:
Labels: -Patch-new Patch-review
Comment #4 on issue 2029 by pkx1...@gmail.com: Patch: Adds some info about
pure properties to the CG.
http://code.google.com/p/lilypond/issues/detail?id=2029
Passes make and a full make doc
___
bug-
Comment #1 on issue 1906 by thomaspu...@gmail.com: Build fails on Fedora
http://code.google.com/p/lilypond/issues/detail?id=1906
Are you building it on a multicore box. Try using one processor only.
This si still a problem with 2.15.17 on Mageia, but this workaround let me
build it.
___
Updates:
Labels: -Patch-new Patch-needs_work
Comment #4 on issue 2033 by pkx1...@gmail.com: Patch: This removes
ly:export for real and separates read/eval for Scheme expressions.
http://code.google.com/p/lilypond/issues/detail?id=2033
This fails make (petty instantly actually)
--snip
Comment #4 on issue 2032 by pkx1...@gmail.com: Patch: Fold
set-time-signature into \time
http://code.google.com/p/lilypond/issues/detail?id=2032
Let me know if you want me to test this against current master and what I
need to change in VERSION (if I still need to do this). James
___
Updates:
Labels: -Patch-new Patch-needs_work
Comment #26 on issue 2000 by pkx1...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000
Doesn't pass make
--snip--
[/home/jlowe/lilypond-git/build/out/share/lilypond/current/s
Comment #25 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c25
Fixes NoteColumn vs SpanBar collisions.
http://codereview.appspot.com/5323062
___
bug-lilypo
Updates:
Labels: Patch-new
Comment #24 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c24
Fixes NoteColumn vs SpanBar collisions.
http://codereview.appspot.com/5323062
___
Updates:
Status: Fixed
Labels: -Patch-new Fixed_2_5_18
Comment #8 on issue 1875 by d...@gnu.org: tests for flower appear to miss
instantiations of classes
http://code.google.com/p/lilypond/issues/detail?id=1875
In order to preserve my own sanity, I pushed a somewhat streamline
Comment #3 on issue 2032 by d...@gnu.org: Patch: Fold set-time-signature
into \time
http://code.google.com/p/lilypond/issues/detail?id=2032
No longer blocked on issue 2024 (which has made it into master), but still
requires another bump of VERSION before possible to test unmodified.
Grah
Comment #3 on issue 2033 by d...@gnu.org: Patch: This removes ly:export for
real and separates read/eval for Scheme expressions.
http://code.google.com/p/lilypond/issues/detail?id=2033
Can we get test coverage on this one? The blocking issus is in master, and
the VERSION is sufficient for
Status: Accepted
Owner:
Labels: Warning
New issue 2036 by d...@gnu.org: make test in flower subdirectory produces
lots of warnings with g++ 4.6
http://code.google.com/p/lilypond/issues/detail?id=2036
See attached log file.
Attachments:
flower-test.log 7.3 KB
_
Updates:
Status: Invalid
Comment #1 on issue 2035 by d...@gnu.org: flower/include/yaffut.hh is
distributed without license
http://code.google.com/p/lilypond/issues/detail?id=2035
www.boost.org just came online again, and the link works. The license
looks like simplified BSD (namely
Status: Accepted
Owner:
Labels: Type-Other
New issue 2035 by d...@gnu.org: flower/include/yaffut.hh is distributed
without license
http://code.google.com/p/lilypond/issues/detail?id=2035
The file says at the top:
// Copyright 2006 Rutger E.W. van Beusekom.
// Distributed under the Boost
Updates:
Labels: Patch-new
Comment #7 on issue 1875 by d...@gnu.org: tests for flower appear to miss
instantiations of classes
http://code.google.com/p/lilypond/issues/detail?id=1875#c7
Keep yaffut from attempting to demangle.
Issue 1875
One can get the pretty output by piping the r
Updates:
Labels: -Patch-review Patch-needs_work
Comment #27 on issue 1567 by pkx1...@gmail.com: Add documentation for
footnotes
http://code.google.com/p/lilypond/issues/detail?id=1567
Colin,
Mike did answer them, I need to make a new patch. Thanks.
James
__
33 matches
Mail list logo
