> Hmm, that brings to mind a different possible solution:
>
> @macro lilyfile{\FILENAME\}
> @/@file{\FILENAME\}
> @end macro
>
> if there's no way to automate our desired behaviour (assuming we
> can agree on a desired formatting in the output!), this might be
> an alternate solution?
It is ver
http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely#newcode844
Documentation/notation/changing-de
Correct typo
http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely#newcode843
Documentation/notati
On 11/07/12 15:38, Mike Blackstock wrote:
I have a Lilypond 'Cloud' web service to announce shortly as well, if anyone
wants to have a look.
It's at http://cloud.blackstockweb.ca - email login 'guest' password 'guest'
It's functional enough for people to be able to upload their Lilypond projec
Graham Percival writes:
> On Wed, Jul 11, 2012 at 10:32:28PM +0200, David Kastrup wrote:
>> "Phil Holmes" writes:
>>
>> > David doesn't like @* so I avoided it. I'll use @*
>>
>> @* is awful. It cuts the current line _short_ unconditionally which
>> means that we may get abysmally bad breaks
Graham Percival writes:
> On Wed, Jul 11, 2012 at 10:28:35PM +0200, David Kastrup wrote:
>> More like
>>
>> --- linewidth --
>> Thisisaparagraph
>> which has a really long
>> word and has benefitted
>> from some kind of
>> emergency-stretch-tweak
>> w
On Wed, Jul 11, 2012 at 10:32:28PM +0200, David Kastrup wrote:
> "Phil Holmes" writes:
>
> > David doesn't like @* so I avoided it. I'll use @*
>
> @* is awful. It cuts the current line _short_ unconditionally which
> means that we may get abysmally bad breaks when the paragraph content
> chan
On Wed, Jul 11, 2012 at 10:28:35PM +0200, David Kastrup wrote:
> More like
>
> --- linewidth --
> Thisisaparagraph
> which has a really long
> word and has benefitted
> from some kind of
> emergency-stretch-tweak
> which isn't IMO exactly what
> we wa
"Phil Holmes" writes:
>> @*
>> @file{blah}
>
> David doesn't like @* so I avoided it. I'll use @*
@* is awful. It cuts the current line _short_ unconditionally which
means that we may get abysmally bad breaks when the paragraph content
changes. It makes more sense to use @/ which merely permi
Janek Warchoł writes:
> From what i understand (based on David's description) the result in
> second case would rather be
>
> --- linewidth --
> This is a paragraph which
> has a really long word and
> has benefitted from some
> kind of
> emergency-stretc
- Original Message -
From:
To: ; ;
; ;
Cc: ;
Sent: Wednesday, July 11, 2012 8:45 PM
Subject: Re: Fixes all black bars in NR (issue 6345088)
I've only looked at the first few files, but I have grave concerns with
this patch.
I feel terrible about it, though. Please, PLEASE, anybod
>From what i understand (based on David's description) the result in
second case would rather be
--- linewidth --
This is a paragraph which
has a really long word and
has benefitted from some
kind of
emergency-stretch-tweak
which isn't IMO exactly what
we
On Wed, Jul 11, 2012 at 09:45:49PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > Sure. So we're asking if TeX can be tweaked to consider
> > additional solutions. (namely, "always add a line-break before
> > anything with an overfull hbox, regardless of what that makes the
> > res
Janek Warchoł writes:
> On Wed, Jul 11, 2012 at 9:45 PM, David Kastrup wrote:
>> Graham Percival writes:
>>> Sure. So we're asking if TeX can be tweaked to consider
>>> additional solutions. (namely, "always add a line-break before
>>> anything with an overfull hbox, regardless of what that m
On Wed, Jul 11, 2012 at 9:45 PM, David Kastrup wrote:
> Graham Percival writes:
>> Sure. So we're asking if TeX can be tweaked to consider
>> additional solutions. (namely, "always add a line-break before
>> anything with an overfull hbox, regardless of what that makes the
>> rest of that parag
Graham Percival writes:
> On Wed, Jul 11, 2012 at 03:50:21PM +0200, David Kastrup wrote:
>> Janek Warchoł writes:
>>
>> > On Wed, Jul 11, 2012 at 1:56 PM, David Kastrup wrote:
>> >>
>> >> "Phil Holmes" writes:
>> >> > It should wrap between the words "the file" and the filename.
>
> +1
>
>> >
I've only looked at the first few files, but I have grave concerns with
this patch.
I feel terrible about it, though. Please, PLEASE, anybody who wants to
make lots of changes to the docs -- spend *at most* one hour working on
your changes, then submit them to get feedback. It must have taken a
On Mon, Jul 9, 2012 at 7:10 PM, Werner LEMBERG wrote:
>
>> I suggest that we adopt this as an official policy: fixes for
>> easy-to-overlook things should be documented by regtests using
>> big/enormous font-size (e.g. between 30 and 100, depending on
>> issue). So, everyone checking regtests sho
On Wed, Jul 11, 2012 at 03:50:21PM +0200, David Kastrup wrote:
> Janek Warchoł writes:
>
> > On Wed, Jul 11, 2012 at 1:56 PM, David Kastrup wrote:
> >>
> >> "Phil Holmes" writes:
> >> > It should wrap between the words "the file" and the filename.
+1
> > It would probably be less ugly that an
LGTM
http://codereview.appspot.com/6353081/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Wed, Jul 11, 2012 at 6:57 PM, Phil Holmes wrote:
> This prompted me to check my indexing and it was mostly OK, but I found that
> adding an index on RateUsername improves the speed of this query by a factor
> of about 4. I think we're back to pretty much OK now.
Yeah, previous delay was a bit
On Wed, Jul 11, 2012 at 6:07 PM, David Kastrup wrote:
> Janek Warchoł writes:
>
>> What about something like this:
>> when a regression against latest stable is found, it's not marked as
>> critical (as Graham suggests). However, when we make a stable
>> release, all regressions present in the t
This prompted me to check my indexing and it was mostly OK, but I found that
adding an index on RateUsername improves the speed of this query by a factor of
about 4. I think we're back to pretty much OK now.
If it gets bad, I'll ask for help with my SQL.
--
Phil Holmes
- Original Messa
Janek Warchoł writes:
> On Tue, Jul 10, 2012 at 11:50 PM, Trevor Daniels
> wrote:
>> So far there have been c. 75 critical regressions under the
>> current definition of 'critical' since 2.14. All but one have been
>> fixed, many of them promptly. This prompt attention IMO
>> is due only to t
Hi All, Graham,
first, let me apologise for not responding promptly.
Secondly, here's my reply to Graham's almost-original proposition;
i'll send a reply to current discussion ("Clear policy discussions")
separately.
On Tue, Jun 26, 2012 at 10:55 PM, Graham Percival
wrote:
> Let’s drop the “any
- Original Message -
From:
To: ; ;
;
Cc: ;
Sent: Wednesday, July 11, 2012 4:23 PM
Subject: Re: Fixes all black bars in NR (issue 6345088)
LGTM. Thanks a lot!
http://codereview.appspot.com/6345088/diff/1/Documentation/snippets/simultaneous-headword.ly
File Documentation/snippet
LGTM. Thanks a lot!
http://codereview.appspot.com/6345088/diff/1/Documentation/snippets/simultaneous-headword.ly
File Documentation/snippets/simultaneous-headword.ly (right):
http://codereview.appspot.com/6345088/diff/1/Documentation/snippets/simultaneous-headword.ly#newcode16
Documentation/sn
Also if you want to give more details about your database, e.g., which SQL
implementation, how the tables are organised, and the code you tried, maybe
someone here can improve it.
On Jul 10, 2012 4:54 PM, "Trevor Daniels" wrote:
>
> Phil Holmes wrote Tuesday, July 10, 2012 12:03 PM
>
> > Kind-of
I have a Lilypond 'Cloud' web service to announce shortly as well, if
anyone wants to have a look.
It's at http://cloud.blackstockweb.ca - email login 'guest' password 'guest'
It's functional enough for people to be able to upload their Lilypond
projects and be able to work on them and show them
LGTM
Trevor
http://codereview.appspot.com/6345088/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: Graham Percival, Trevor Daniels, J_lowe,
Message:
Lots of changes here. The NR still builds successfully following them
all, so I'm fairly confident, but please review if you have time.
Description:
Just a few changed files. A number of these are in /snippets and I have
updated the
Janek Warchoł writes:
> On Wed, Jul 11, 2012 at 1:56 PM, David Kastrup wrote:
>>
>> "Phil Holmes" writes:
>> > It should wrap between the words "the file" and the filename.
>>
>> Obviously not enough stretchability for that to fit. You can try
>>
>> @tex
>> \global\emergencystretch=5in
>> @end
On Wed, Jul 11, 2012 at 1:56 PM, David Kastrup wrote:
>
> "Phil Holmes" writes:
> > It should wrap between the words "the file" and the filename.
>
> Obviously not enough stretchability for that to fit. You can try
>
> @tex
> \global\emergencystretch=5in
> @end tex
>
> and see where this gets yo
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Wednesday, July 11, 2012 12:56 PM
Subject: Re: Texinfo help, please
"Phil Holmes" writes:
- Original Message -
From: "David Kastrup"
To:
Sent: Wednesday, July 11, 2012 12:22 PM
Subject: Re: Texinfo
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To:
> Sent: Wednesday, July 11, 2012 12:22 PM
> Subject: Re: Texinfo help, please
>
>
>> "Phil Holmes" writes:
>>
>>> I'm doing a little project to get rid of all the black bars on the
>>> right side of the PDF of
Reviewers: lemzwerg,
Message:
On 2012/07/11 04:15:47, lemzwerg wrote:
http://codereview.appspot.com/6351083/diff/1/Documentation/contributor/lsr-work.itexi
File Documentation/contributor/lsr-work.itexi (right):
http://codereview.appspot.com/6351083/diff/1/Documentation/contributor/lsr-work.i
- Original Message -
From: "David Kastrup"
To:
Sent: Wednesday, July 11, 2012 12:22 PM
Subject: Re: Texinfo help, please
"Phil Holmes" writes:
I'm doing a little project to get rid of all the black bars on the
right side of the PDF of the NR - these indicate material that is too
w
"Phil Holmes" writes:
> I'm doing a little project to get rid of all the black bars on the
> right side of the PDF of the NR - these indicate material that is too
> wide to be properly accommodated on the page. One of the things that
> causes this is text like:
>
> Fret diagrams for the ukulele
I'm doing a little project to get rid of all the black bars on the right
side of the PDF of the NR - these indicate material that is too wide to be
properly accommodated on the page. One of the things that causes this is
text like:
Fret diagrams for the ukulele are contained in the file
@file
http://codereview.appspot.com/6345086/diff/1/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
http://codereview.appspot.com/6345086/diff/1/Documentation/notation/changing-defaults.itely#newcode698
Documentation/notation/changing-defaults
Reviewers: ,
Message:
This is a substantial change. I took the opportunity to
deal with a TODO in the file - document \with - as
this made for a more sensible organisation of the section.
I'd like reviewers to consider in particular
- factual accuracy (I was not confident about some parts)
-
Graham Percival writes:
> On Tue, Jul 10, 2012 at 11:51:11PM +0200, David Kastrup wrote:
>> Graham Percival writes:
>
>
> I'll only address "meta-discussion" points here.
>
>> > What about the next one? Phil has been learning how to do it, and I
>> > certainly won't call *him* a trained monkey.
Patch pushed
bcd9d85bfc1dd6cc2dd3e98901b4df33fd6d0989
http://codereview.appspot.com/6353079/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
43 matches
Mail list logo
