Re: git cl problem: Couldn’t create Allura issue

- Original Message - From: "Simon Albrecht" To: "Phil Holmes" ; "ly-devel" Sent: Tuesday, December 29, 2015 4:19 PM Subject: Re: git cl problem: Couldn’t create Allura issue On 29.12.2015 15:38, Phil Holmes wrote:

Re: LM 2.4.1: More accurate description of variable naming rules (issue 280560043 by simon.albre...@mail.de)

https://codereview.appspot.com/280560043/diff/20001/Documentation/learning/common-notation.itely File Documentation/learning/common-notation.itely (right): https://codereview.appspot.com/280560043/diff/20001/Documentation/learning/common-notation.itely#newcode1343

Re: Snippet 706: Generating custom flags

>>> pdfTeX warning: pdfetex (file >>> /usr/share/texmf-dist/fonts/type1/public/tex-gyre >>> /qcsr.pfb): glyph `f_i' undefined >> >> Yep, the font in question only contains `fi' and `fl' glyph names. > > How could we fix this? We can't, except using luatex, as suggested by Masamichi-san.

Re: git cl problem: Couldn’t create Allura issue

On 29.12.2015 15:38, Phil Holmes wrote: - Original Message - From: "Simon Albrecht" To: "ly-devel" Sent: Monday, December 28, 2015 10:12 PM Subject: git cl problem: Couldn’t create Allura issue Hello, sorry, but I still don’t seem to

Re: making QUIET_BUILD the default

On 29/12/15 08:52, Werner LEMBERG wrote: > Is there a particular reason to no making `QUIET_BUILD' the default? > For Metafont, it's extremely chatty otherwise... > > On the other hand, I suggest to change > > ifdef QUIET_BUILD > LILYPOND_BOOK_WARN = --loglevel=NONE > else >

Re: Snippet 706: Generating custom flags

pdfTeX warning: pdfetex (file /usr/share/texmf-dist/fonts/type1/public/tex-gyre /qcsr.pfb): glyph `f_i' undefined >>> >>> Yep, the font in question only contains `fi' and `fl' glyph names. >> >> How could we fix this? > > We can't, except using luatex, as suggested by

making QUIET_BUILD the default

Is there a particular reason to no making `QUIET_BUILD' the default? For Metafont, it's extremely chatty otherwise... On the other hand, I suggest to change ifdef QUIET_BUILD LILYPOND_BOOK_WARN = --loglevel=NONE else LILYPOND_BOOK_WARN = --loglevel=WARN endif to ifdef QUIET_BUILD

Re: Snippet 706: Generating custom flags

In the PDF version of the snippet above, the "fl" letters of "flag" are missing. I think this is probably because they are being converted to a ligatured glyph, and then not displaying. Anyone know how to prevent this from happening? >>> >>> If I understand correctly, it is

Re: making QUIET_BUILD the default

Am 29.12.2015 um 09:52 schrieb Werner LEMBERG: Is there a particular reason to no making `QUIET_BUILD' the default? For Metafont, it's extremely chatty otherwise... I prefer a verbose build and a script to save the chatty output to a logfile: #!/bin/bash RED='\033[0;31m' NOC='\033[0m'

Re: Snippet 706: Generating custom flags

- Original Message - From: "Werner LEMBERG" To: Cc: ; Sent: Tuesday, December 29, 2015 11:38 AM Subject: Re: Snippet 706: Generating custom flags In the PDF version of the snippet above, the "fl"

Re: Snippet 706: Generating custom flags

>> In the PDF version of the snippet above, the "fl" letters of "flag" >> are missing. I think this is probably because they are being >> converted to a ligatured glyph, and then not displaying. Anyone >> know how to prevent this from happening? > > If I understand correctly, it is pdfTeX

Re: git cl problem: Couldn’t create Allura issue

On 28.12.2015 23:26, Thomas Morley wrote: 2015-12-28 23:12 GMT+01:00 Simon Albrecht : What does ~/git-cl (master)$ gitk show? For me it returns the attached screenshot (my git-cl is _not_ up to date, working, though) If you're behind the most recent shown commit

Re: making QUIET_BUILD the default

>> Is there a particular reason to no making `QUIET_BUILD' the >> default? For Metafont, it's extremely chatty otherwise... > > I prefer a verbose build and a script to save the chatty output to a > logfile: Well, the Metafont logging data is *always* saved to files (`mf/out/*.log')!

Re: git cl problem: Couldn’t create Allura issue

- Original Message - From: "Simon Albrecht" To: "ly-devel" Sent: Monday, December 28, 2015 10:12 PM Subject: git cl problem: Couldn’t create Allura issue Hello, sorry, but I still don’t seem to get along with git cl. I just uploaded a