Re: Running fixcc.py

2020-03-23 Thread Dan Eble
On Mar 23, 2020, at 18:41, David Kastrup  wrote:
> 
> Dan Eble  writes:
> 
>> I'll submit that for review along with some tweaks to the clang-format
>> configuration.  I still have some testing to do.
> 
> Thanks, and sorry for causing that workload out of not really thinking
> through things.

Think nothing of it.  I prefer Ubuntu's latest package over a 7-year-old source 
tarball from SourceForge.

https://codereview.appspot.com/551640043/
— 
Dan




Re: Running fixcc.py

2020-03-23 Thread David Kastrup
Dan Eble  writes:

> On Mar 23, 2020, at 17:10, David Kastrup  wrote:
>> 
>> Dan Eble  writes:
>
>>> As far as I'm concerned, we could just declare 3.1 to be the new
>>> preferred version.  I'm not sure whether that would inconvenience
>>> anyone else, though.
>> 
>> It's the current version, so eventually it might have become a candidate
>> anyway.  If we do that, fixcc should probably be changed such that 3.1
>> is the version accepted without --sloppy .
>
> I'll submit that for review along with some tweaks to the clang-format
> configuration.  I still have some testing to do.

Thanks, and sorry for causing that workload out of not really thinking
through things.

-- 
David Kastrup



Re: Running fixcc.py

2020-03-23 Thread Dan Eble
On Mar 23, 2020, at 17:10, David Kastrup  wrote:
> 
> Dan Eble  writes:

>> As far as I'm concerned, we could just declare 3.1 to be the new
>> preferred version.  I'm not sure whether that would inconvenience
>> anyone else, though.
> 
> It's the current version, so eventually it might have become a candidate
> anyway.  If we do that, fixcc should probably be changed such that 3.1
> is the version accepted without --sloppy .

I'll submit that for review along with some tweaks to the clang-format 
configuration.  I still have some testing to do.
— 
Dan




Re: make builds everything

2020-03-23 Thread Dan Eble
On Mar 23, 2020, at 10:06, Jean-Charles Malahieude  wrote:
> 
> Le 21/03/2020 à 18:11, Malte Meyn a écrit :
>> Hi list,
>> first of all, I’d like thank those who made the make output less verbose, 
>> this makes errors much easier to find. 
> 
> It is, unfortunately, sometimes too little verbose: say I've omitted a 
> closing 
...
> How would it be possible to access the Nirvana, or to reinstate some 
> verbosity in this case, with:

make VERBOSE=1 ...
(Verbosity, not Nirvana.)

Regards,
— 
Dan




Re: Running fixcc.py

2020-03-23 Thread David Kastrup
Dan Eble  writes:

> On Mar 22, 2020, at 17:04, David Kastrup  wrote:
>> 
>> Dan Eble  writes:
>> 
>>> Did you use astyle 2.04 or another version?  I built 2.04 from source
> ...
>> 3.1.  I am afraid that I may have updated my system since the review,
> ...
>> So where should we go from here?
>
> As far as I'm concerned, we could just declare 3.1 to be the new
> preferred version.  I'm not sure whether that would inconvenience
> anyone else, though.

It's the current version, so eventually it might have become a candidate
anyway.  If we do that, fixcc should probably be changed such that 3.1
is the version accepted without --sloppy .

-- 
David Kastrup



Re: make builds everything

2020-03-23 Thread Jean-Charles Malahieude

Le 21/03/2020 à 18:11, Malte Meyn a écrit :

Hi list,

first of all, I’d like thank those who made the make output less 
verbose, this makes errors much easier to find. 


It is, unfortunately, sometimes too little verbose: say I've omitted a 
closing brace in a texinfo @-command. The only thing I get is


[…]
Making Documentation/fr/out-www/translation-lily-images (hard links)

Please check the logfile

  /home/jcharles/GIT/Traduc/Documentation/fr/notation.texi2pdf.log

for errors

make[3]: *** 
[/home/jcharles/GIT/Traduc/stepmake/stepmake/texinfo-rules.make:85: 
out-www/notation.pdf] Error 1

make[3]: *** Deleting file 'out-www/notation.pdf'
make[2]: *** 
[/home/jcharles/GIT/Traduc/stepmake/stepmake/generic-targets.make:167: 
WWW-1] Error 2
make[1]: *** 
[/home/jcharles/GIT/Traduc/stepmake/stepmake/generic-targets.make:167: 
WWW-1] Error 2
make: *** 
[/home/jcharles/GIT/Traduc/stepmake/stepmake/generic-targets.make:185: 
doc-stage-1] Error 2


Compilation exited abnormally with code 2 at Mon Mar 23 14:40:40
[end of terminal output]

and at the bottom of notation.texi2pdf.log

[919][920][921][922]
4893652 bytes written
/usr/bin/texi2dvi: 
/home/jcharles/GIT/Traduc/scripts/build/out/xetex-with-options exited 
with bad status, quitting.


As I've updated some files, I would have preferred the old way
instead of, like with .ly files, trying to obtain a MWE !

How would it be possible to access the Nirvana, or to reinstate some 
verbosity in this case, with:


[484][485][486]
2455109 bytes written

/home/jcharles/GIT/Stable/Documentation/fr/out-www/notation/world.texi:53: 
Emer

gency stop.

   @par
l.53


Cheers,
--
Jean-Charles



Re: Issue #5822 aftermath: download sizes are gone from web site

2020-03-23 Thread David Kastrup
David Kastrup  writes:

> Han-Wen Nienhuys  writes:
>
>> The website uses scripts that aren't directly checked out from
>> savannah, so you can't directly compromise the webserver through code
>> commits.
>>
>> I can update the scripts.
>
> Any chance of giving this a try now?  The stuff is in master's script
> now.
>
> Thanks!

Ping?

-- 
David Kastrup



PATCHES - Countdown for March 23rd

2020-03-23 Thread pkx166h

Hello,

Here is the current patch countdown list. The next countdown will be on

March 25th


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:

5860 Remove unused file - Han-Wen Nienhuys
https://sourceforge.net/p/testlilyissues/issues/5860
http://codereview.appspot.com/571900048

5858 Cleanup flower/ makefile - Han-Wen Nienhuys
https://sourceforge.net/p/testlilyissues/issues/5858
http://codereview.appspot.com/577700045

5857 Inline elisp stepmake templates. - Han-Wen Nienhuys
https://sourceforge.net/p/testlilyissues/issues/5857
http://codereview.appspot.com/563780044

5856 Run find -name \*.scm -exec scripts/auxiliar/fixscm.sh {} + - David 
Kastrup

https://sourceforge.net/p/testlilyissues/issues/5856
http://codereview.appspot.com/555490045

5855 Stop installing TFM and Type1 fonts. - Han-Wen Nienhuys
https://sourceforge.net/p/testlilyissues/issues/5855
http://codereview.appspot.com/577700043

5854 Remove trailing whitespace {python,scm,lily,scripts}. - Han-Wen 
Nienhuys

https://sourceforge.net/p/testlilyissues/issues/5854
http://codereview.appspot.com/547810043

5853 Cleanup python/ build rules. - Han-Wen Nienhuys
https://sourceforge.net/p/testlilyissues/issues/5853
http://codereview.appspot.com/549740043

5851 .dir-locals.el: no indent-tabs-mode in shell-script-mode - David 
Kastrup

https://sourceforge.net/p/testlilyissues/issues/5851
http://codereview.appspot.com/575840047

5850 Remove input/regression/test-output-distance.ly - Han-Wen Nienhuys
https://sourceforge.net/p/testlilyissues/issues/5850
http://codereview.appspot.com/575850043

5849 aclocal.m4: Support GUILE_CONFIG, document GUILE_FLAVOR - David Kastrup
https://sourceforge.net/p/testlilyissues/issues/5849
http://codereview.appspot.com/575860044

5844 scripts/build/scan-mf-deps: script to generate MF dependencies - 
Han-Wen Nienhuys

https://sourceforge.net/p/testlilyissues/issues/5844
http://codereview.appspot.com/553700043

5836 Added transition lines for lyrics - David Grant
https://sourceforge.net/p/testlilyissues/issues/5836
http://codereview.appspot.com/565750043

4375 \compressFullBarRests should be renamed - Valentin Villenave
https://sourceforge.net/p/testlilyissues/issues/4375
http://codereview.appspot.com/553750044


 Review:

5861 Trim unused toplevel targets. - Han-Wen Nienhuys
https://sourceforge.net/p/testlilyissues/issues/5861
http://codereview.appspot.com/547810069

5859 Inline scm stepmake templates - Han-Wen Nienhuys
https://sourceforge.net/p/testlilyissues/issues/5859
http://codereview.appspot.com/575870044

5852 Inline executable-* stepmake templates in lily/GNUmakefile - 
Han-Wen Nienhuys

https://sourceforge.net/p/testlilyissues/issues/5852
http://codereview.appspot.com/577690043


 New:

No new patches at this time.


 Waiting:

5811 mf: use python scripting for generating Emmentaler fonts - Han-Wen 
Nienhuys

https://sourceforge.net/p/testlilyissues/issues/5811
http://codereview.appspot.com/553580043

5771 remove unnecessary (descend-to-context ... 'Score) - Dan Eble
https://sourceforge.net/p/testlilyissues/issues/5771
http://codereview.appspot.com/557440043

5740 Add \post to defer context actions to end of time step - Dan Eble
https://sourceforge.net/p/testlilyissues/issues/5740
http://codereview.appspot.com/581600043





***



Regards,

James





Re: definitions in macros?

2020-03-23 Thread Han-Wen Nienhuys
On Sun, Mar 22, 2020 at 10:09 PM David Kastrup  wrote:
> > In the code below, it looks like only one of the two definitions in
> > the body of my-macro-new takes effect. Is this expected, and if so,
> > why?
> >
> > (defmacro-public my-macro-old (command-and-args . definition)
> >   (module-define! (current-module) 'x1 "I am X1\n")
> >   (module-define! (current-module) 'x2 "I am X2\n"))
> >
> > (defmacro-public my-macro-new (command-and-args . definition)
> > `(define p "i am P\n")
> > `(define q "i am Q\n"))
>
> This is very much expected.  The macro body contains two side-effect
> free expressions (namely quoted lists) and returns the last one which is
..
> You probably wanted something like
>   `(begin (define p ...) (define q ...))

d'oh! I am an idiot.

Thanks,

-- 
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen