Re: Please test gub

>> If we get more success reports, the resulting packages should be >> uploaded so that other people not running gub can test them. >> Developers can then have a look how to add support for 64bit >> binaries on MacOS and Windows. Especially the former is rather >> urgent... > > I can upload my st

Re: Please test gub

Am 29.01.19 um 08:14 schrieb Werner LEMBERG: The overall end doesn't report a failure, but the last "rule" shows some problems, I should have mentioned this was the "nsis rule" If you reach this point you can be rather sure that everything was fine – at least for your build system, since it wa

Re: Please test gub

>> The overall end doesn't report a failure, but the last "rule" shows >> some problems, > > I should have mentioned this was the "nsis rule" If you reach this point you can be rather sure that everything was fine – at least for your build system, since it was used to run lilypond's tests to gen

Re: Please test gub

On 29.01.19 00:53, Karlin High wrote: On 1/28/2019 6:53 AM, Knut Petersen wrote: Please report success / fails with os / version / cpu info. I really like the simple instructions you posted, Knut. I wouldn't be testing Gub without them. My setup doesn't like the darwin-ppc::odcctools package f

Re: Emacs lilypond mode

>> Formatting only. No change in behaviour. > > And grammar and wording changes in the comments and changes from ## > comments to # comments (which does not appear to make a difference > to Emacs though as opposed to comments in some other languages). Yes. `#' and `##' were mixed up without a

Re: Please test gub

Am 29.01.19 um 07:41 schrieb Urs Liska: The overall end doesn't report a failure, but the last "rule" shows some problems, I should have mentioned this was the "nsis rule" ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.

Re: Please test gub

Hi Knut, thank you for working on this, and - like Karlin - I wouldn't have tested without your straightforward recipe. But before going to bed I logged off, then logged in again in a terminal-only session and started the process. Am 28.01.19 um 13:53 schrieb Knut Petersen: Hi everybody! I

Re: Please test gub

Il giorno mar 29 gen 2019 alle 0:53, Karlin High ha scritto: building package: darwin-ppc::odcctools *** Stage: download (odcctools, darwin-ppc) *** Stage: untar (odcctools, darwin-ppc) Command barfed: tar -C /home/karlin/knut-gub/gub/target/darwin-ppc/src/odcctools-278 --strip-compone

Re: Emacs lilypond mode

Werner LEMBERG writes: >> PS: I'll fix the `yyout2grammar' script. Done, see https://sourceforge.net/p/testlilyissues/issues/5468/ >>> >>> So what is >>> >>> >>> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=385ed0864c1be511ce16eb21751cec7fb68dd978 >>

Re: Please test gub

On 1/28/2019 6:53 AM, Knut Petersen wrote: Please report success / fails with os / version / cpu info. I really like the simple instructions you posted, Knut. I wouldn't be testing Gub without them. My setup doesn't like the darwin-ppc::odcctools package for some reason. Mystified why it's b

Re: guilev1/2 musing

Am Mo., 28. Jan. 2019 um 23:50 Uhr schrieb Valentin Villenave : > > On 1/25/19, Thomas Morley wrote: > > how exactly is your guile-2-setup, simply checkout the > > 'guile-v2-work'-branch, rebase and compile? > > Oh, I wasn’t even keeping track of this branch (isn’t it dormant, much > like Patrick’

Re: Emacs lilypond mode

PS: I'll fix the `yyout2grammar' script. > > http://lists.gnu.org/archive/html/bug-lilypond/2018-01/msg00010.html Ah, I have missed this completely, and/or couldn't remember your work. Thanks for the link! Unfortunately, `lists.gnu.org' distorts stuff in text attachments that contain `@' i

Re: Emacs lilypond mode

> PS: I'll fix the `yyout2grammar' script. >>> >>> Done, see >>> >>>https://sourceforge.net/p/testlilyissues/issues/5468/ >> >> So what is >> >> >> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=385ed0864c1be511ce16eb21751cec7fb68dd978 >> >> all about Formatting only. N

Re: guilev1/2 musing

On 1/25/19, Thomas Morley wrote: > how exactly is your guile-2-setup, simply checkout the > 'guile-v2-work'-branch, rebase and compile? Oh, I wasn’t even keeping track of this branch (isn’t it dormant, much like Patrick’s previous work on Guilev2?); I’m just using master with --enable-guile2, whi

Re: Add `TEX` environemnt variable for texi2pdf (issue 353870043 by truer...@gmail.com)

On 2019/01/28 21:44:11, lemzwerg wrote: LGTM, thanks! I agree, LGTM. I'll do an strace gub build tomorrow to verify that no hidden use of etex was missed. If the patch passes the strace test it would be an immediate candidate for both master and stable/2.20. https://codereview.appspot.com/35

Re: Please test gub

Hi James! I'd like to help here if I can. Thanks However at home I am on metered internet and it appears that after make lilypond it starts to download files? Can you tell me approximately how large the data that will be downloaded is - speed of download isn't an issue, just the amount.

Re: New feature: automatically invert chords or drop/rise chord notes (issue 365840043 by v.villen...@gmail.com)

On 2019/01/28 20:02:53, Valentin Villenave wrote: I can’t figure out how to make it work without resetting the EventChord’s elements list. How would you proceed? Without any pointer to what you are having problems with, this is essentially "do it yourself". Sigh. I don't even understand wh

Add `TEX` environemnt variable for texi2pdf (issue 353870043 by truer...@gmail.com)

LGTM, thanks! https://codereview.appspot.com/353870043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: New feature: automatically invert chords or drop/rise chord notes (issue 365840043 by v.villen...@gmail.com)

On 2019/01/23 22:30:25, dak wrote: Shouldn't you consider preexisting octavation for sorting the pitches? Duh. That looks like a mess. Don't you rather intend to sort the _notes_? Sure. I figured in a chord, notes wouldn’t carry individual properties… but they do, of course. list-set! her

Re: Doc: add markup objects overview (issue 357930043 by v.villen...@gmail.com)

On 2019/01/24 21:11:20, Valentin Villenave wrote: Address Werner’s suggestions. This is a rather trivial amendment, so if nobody has any further objection, I suggesting pushing it onto the countdown list… https://codereview.appspot.com/357930043/ ___

Re: Please test gub

Hello, On 28/01/2019 12:53, Knut Petersen wrote: Hi everybody! I created a branch in my gub repository  that contains https://github.com/gperciva plus pull requests 53-60. Therefore it is pretty easy to test if that version of gub succeeds to build current lilypond master on your machine.

Re: Emacs lilypond mode

On 28/01/2019 11:33, Werner LEMBERG wrote: PS: I'll fix the `yyout2grammar' script. Done, see https://sourceforge.net/p/testlilyissues/issues/5468/ So what is http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=385ed0864c1be511ce16eb21751cec7fb68dd978 all about I didn't see

Re: Please test gub

Hi Federico! I've already tested this setup on Debian 9, Ubuntu 16.04, Fedora 29 (with gcc-7) and reported the errors. Yes, an additional commit (added yesterday) in pull request #58 should solve the problem with a failing gs Knut ___ lilypo

Re: Please test gub

Il giorno lun 28 gen 2019 alle 13:53, Knut Petersen ha scritto: Hi everybody! I created a branch in my gub repository that contains plus pull requests 53-60. Therefore it is pretty easy to test if that version of gub succeeds to build current lilypond maste

Re: Emacs lilypond mode

See also http://lists.gnu.org/archive/html/bug-lilypond/2018-01/msg00010.html Cheers, Robin On 28.01.2019 12:33, Werner LEMBERG wrote: PS: I'll fix the `yyout2grammar' script. Done, see https://sourceforge.net/p/testlilyissues/issues/5468/ You might want to check whether Bison now o

Please test gub

Hi everybody! I created a branch in my gub repository  that contains https://github.com/gperciva plus pull requests 53-60. Therefore it is pretty easy to test if that version of gub succeeds to build current lilypond master on your machine. All you need to do is to execute the following comma

Re: Emacs lilypond mode

Werner LEMBERG writes: >>> PS: I'll fix the `yyout2grammar' script. > > Done, see > > https://sourceforge.net/p/testlilyissues/issues/5468/ > >> You might want to check whether Bison now offers some output option >> that is more dependable than its debug output. > > I haven't seen related to th

Re: Emacs lilypond mode

>> PS: I'll fix the `yyout2grammar' script. Done, see https://sourceforge.net/p/testlilyissues/issues/5468/ > You might want to check whether Bison now offers some output option > that is more dependable than its debug output. I haven't seen related to this in the last version announcements

Re: Flaw in note-by-number, how to catch paper in \book ?

Am Mo., 28. Jan. 2019 um 06:28 Uhr schrieb Ben Rudiak-Gould : > > On Sun, Jan 27, 2019 at 4:40 AM David Kastrup wrote: >> >> layout-set-staff-size does not work properly anyway IIRC. This is >> probably only one symptom. > > > It may have problems inside \layout { ... } but in this example it's u