“Make […] work for *me*” sounds as if this isn’t a general problem? I
don’t know *anything* about emacs (except that vim is superior :P) but
googling c-default-style makes me wonder whether this isn’t only a
problem of your emacs config.
Is it possible that this patch breaks the behaviour for som
https://codereview.appspot.com/337520043/diff/1/input/regression/departure-mark-instrumental.ly
File input/regression/departure-mark-instrumental.ly (right):
https://codereview.appspot.com/337520043/diff/1/input/regression/departure-mark-instrumental.ly#newcode4
input/regression/departure-mark-i
Very nice idea!
On the other hand, \goTo seems unlikely to resemble whatever
we settle on for the grob name… unless everyone likes GoToScript.
What about \jumpTo? Note that I like \goTo also, and I don't mind if
the low-level stuff uses `depart' in its name.
https://codereview.appspot.com/3
On Feb 6, 2018, at 21:12, Simon Albrecht wrote:
>
> Brainstorming (NB, only brainstorming) on the name:
>
> Normal rehearsal marks refer to the beginning of a section, while these refer
> to the end of a section, so an input command might be \endMark "D.S.". You
> still have to complete it to
Brainstorming (NB, only brainstorming) on the name:
Normal rehearsal marks refer to the beginning of a section, while these
refer to the end of a section, so an input command might be \endMark
"D.S.". You still have to complete it to ‘end-of-section mark’ in your
head, but \depart seems far to
Reviewers: ,
Message:
I would be happy to hear suggestions for the name of this command.
My opinion is that \depart is a reasonable name when used for the likes
of D.C., D.S., and "2nd time to Coda" but \depart "Fine" is slightly
weird (departing to nowhere?).
Description:
https://sourceforge.
Hi,
quite often I use custom-grob-properties to get my codings work, like here
http://lsr.di.unimi.it/LSR/Item?id=1032
I'm aware there are reservations about doing this a lot.
Using `details.custom-property' seems to be another way.
An admittedly silly, but close to minimal example, only demonst
Out of my own testings as well as running a full `make doc' with
guilev2:
LGTM
https://codereview.appspot.com/334460043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
2018-02-06 13:17 GMT+01:00 James Lowe :
> Hello,
>
> On Mon, 5 Feb 2018 22:36:51 +0100, Thomas Morley
> wrote:
>
>> Hi,
>>
>> I'm still trying to get make doc work again for my guilev2 setup.
>> It now fails at a point I'm not able to surely track down.
>>
>> The only suspicious in the log I'm po
2018-02-04 1:24 GMT+01:00 David Kastrup :
> Thomas Morley writes:
>
>> 2018-02-04 0:08 GMT+01:00 David Kastrup :
>>
>>> Huh. Not so simple: there are a few define-public called with
>>> constructed names. I'll have to see what kind of non-syntax equivalents
>>> are available for those. Will tak
Jean-Charles Malahieude writes:
> Hi all,
>
> Trying to compile one of Nicolas Sceaux' score, I get a core dump.
>
> Strange thing is the message, depending on the binary:
>
> with the downloaded and installed 2.19.80, it says
>
> lilypond:
> /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.
Hello,
Here is the current patch countdown list. The next countdown will be on
February 9th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push: No patches to push at this time.
Countdown:
5271 Make emacs C++ s
Hi all,
Trying to compile one of Nicolas Sceaux' score, I get a core dump.
Strange thing is the message, depending on the binary:
with the downloaded and installed 2.19.80, it says
lilypond:
/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/lily/script
Hello,
On Mon, 5 Feb 2018 22:36:51 +0100, Thomas Morley
wrote:
> Hi,
>
> I'm still trying to get make doc work again for my guilev2 setup.
> It now fails at a point I'm not able to surely track down.
>
> The only suspicious in the log I'm pointed to is:
>
> Processing `./15/lily-ef5769c9.ly'
2018-02-05 23:59 GMT+01:00 Thomas Morley :
> 2018-02-05 23:48 GMT+01:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>>>
Uh, you are aware that your log ends with:
Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core
15 matches
Mail list logo
