Hi Harm,
On 4/15/15 4:30 PM, "Thomas Morley" wrote:
>Hi Carl,
>
>before going into details, let us decide how to proceed.
>
>The current patch was intended to be not more than maintaining the
>stuff different.
>First step seemed to me putting the needed data into an alist.
>
>2015-04-13 4:22 GMT
On 2015/04/15 06:26:02, Valentin Villenave wrote:
Perhaps you could add a regtest demonstrating this feature (or add a
dotted+accidental note to parenthesize.ly)? Just in case it breaks
again in the
future.
Actually, I had a regtest done and had tested it on my machine, but I
didn't do my gi
Thomas Morley writes:
> Hi,
>
> exploring chordnaming further, I thought it might be nice, if a
> formating procedures for ChordNames could be used in a markup-command
> outputting equal designed chord-names.
>
> Though, looks like I have a problem:
>
> #(display-scheme-music #{ \chordmode { c:m
Hi,
exploring chordnaming further, I thought it might be nice, if a
formating procedures for ChordNames could be used in a markup-command
outputting equal designed chord-names.
Though, looks like I have a problem:
#(display-scheme-music #{ \chordmode { c:m } #})
works ofcourse.
But for
#(defin
Hello,
Here is the current patch countdown list. The next countdown will be on
April 18th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch
_
Patch on countdown for April 18th
https://codereview.appspot.com/224800043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Carl,
before going into details, let us decide how to proceed.
The current patch was intended to be not more than maintaining the
stuff different.
First step seemed to me putting the needed data into an alist.
2015-04-13 4:22 GMT+02:00 :
> It seems to me that this patch is mostly maintainin
On 4/14/2015 7:41 AM, Marco Atzeri wrote:
64 bit "make doc" on 2.19.18 was completed.
on 32 bit I have still issue but much later for a different issue.
Any idea what could cause python to segfault here
or how to debug it ?
make[1]: Leaving directory
'/cygdrive/e/cyg_pub/devel/lilypond/devel
cygwin-python.patch:
Set LDFLAGS to build python module
cygwin-remove-pathconv.patch:
Remove cygwin_conv_to_posix_path
This patch is similar to yours.
>>>
>>> Don't know enough about Cygwin to know whether those two are the right
>>> thing. I'd recomm
>>> cygwin-python.patch:
>>> Set LDFLAGS to build python module
>>>
>>> cygwin-remove-pathconv.patch:
>>> Remove cygwin_conv_to_posix_path
>>> This patch is similar to yours.
>>
>> Don't know enough about Cygwin to know whether those two are the right
>> thing. I'd recommend passi
>>> cygwin-env-TMP.patch:
>>> Don't use environment variable TMP when "make doc"
>>> If I understand correctly,
>>> cygwin system use environment variable TMP for a special purpose.
>>> In other words, on cygwin,
>>> it can not be used for other purpose like Makefile variable.
11 matches
Mail list logo
