Am 23.01.2017 um 23:11 schrieb Simon Albrecht:
> On 23.01.2017 22:47, Urs Liska wrote:
>> So while it's perfectly possible to put OLL projects on the list and to
>> apply for them (or others not listed there) in case of doubt projects
>> working on LilyPond itself might be the preference of the d
Hello,
Here is the current patch countdown list. The next countdown will be on
January 27
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:
5037 web: GSoC page: Add
https://codereview.appspot.com/319150043/diff/1/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
https://codereview.appspot.com/319150043/diff/1/Documentation/notation/changing-defaults.itely#newcode2522
Documentation/notation/changing-d
Hi David!
What a steaming heap of something. So your code would likely have worked in LilyPond 2.16. I think it would make sense to create a new type of stencil expression explicitly intended to bypass outlining. Probably by just containing _two_ stencils: one for typesetting, one for outlining.
Hello David,
On Tue, 24 Jan 2017 07:05:24 -0600
David Nalesnik wrote:
> >
>
> Would you add
>
> 3830 Documentation for \offset is required
> https://sourceforge.net/p/testlilyissues/issues/3830/
> https://codereview.appspot.com/319150043/
For anything to appear on my PATCH countdown (and
James,
On Tue, Jan 24, 2017 at 4:43 AM, James wrote:
> Hello,
>
> Here is the current patch countdown list. The next countdown will be on
> January 27
>
>
> A quick synopsis of all patches currently in the review process can be
> found here:
>
> http://philholmes.net/lilypond/allura/
>
>
>
>
On Tue, Jan 24, 2017 at 7:38 AM, James wrote:
> Hello David,
>
> On Tue, 24 Jan 2017 07:05:24 -0600
> David Nalesnik wrote:
>
>> >
>>
>> Would you add
>>
>> 3830 Documentation for \offset is required
>> https://sourceforge.net/p/testlilyissues/issues/3830/
>> https://codereview.appspot.com/319150
Knut Petersen writes:
> Hi David!
>
>> What a steaming heap of something. So your code would likely have
>> worked in LilyPond 2.16. I think it would make sense to create a new
>> type of stencil expression explicitly intended to bypass
>> outlining. Probably by just containing _two_ stencils: on
David,
Thanks for doing this - I know how hard it is to add a large entry in
the NR (and that is coming from a Native English speaker).
My comments below are, I hope, constructive.
Anything I can do to help you, let me know.
https://codereview.appspot.com/319150043/diff/1/Documentation/notati
Thanks so such for the detailed review! Will post a patch update in the
near future.
https://codereview.appspot.com/319150043/diff/1/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
https://codereview.appspot.com/319150043/diff/1/Docum
Am 24.01.2017 um 14:49 schrieb David Kastrup:
What a steaming heap of something. So your code would likely have
worked in LilyPond 2.16. I think it would make sense to create a new
type of stencil expression explicitly intended to bypass
outlining. Probably by just containing _two_ stencils: on
Knut Petersen writes:
> Am 24.01.2017 um 14:49 schrieb David Kastrup:
>>
What a steaming heap of something. So your code would likely have
worked in LilyPond 2.16. I think it would make sense to create a new
type of stencil expression explicitly intended to bypass
outlining. P
Knut Petersen writes:
> Am 24.01.2017 um 14:49 schrieb David Kastrup:
>>
What a steaming heap of something. So your code would likely have
worked in LilyPond 2.16. I think it would make sense to create a new
type of stencil expression explicitly intended to bypass
outlining. P
Knut Petersen writes:
> Am 24.01.2017 um 14:49 schrieb David Kastrup:
>>
What a steaming heap of something. So your code would likely have
worked in LilyPond 2.16. I think it would make sense to create a new
type of stencil expression explicitly intended to bypass
outlining. P
I've posted an extensive rewrite which hopefully addresses all the
concerns. I think the result is a lot more user-friendly.
Note that I did not change the argument-name "offsets".
My preference would be to use "displacements" here, because I think it
is exactly expressive of its use. The docu
Question:
How do I get a backslash in @subsubsubheading{} ?
The literal symbol doesn't show up, and @backslashchar{} displays
@backslashchar{}
https://codereview.appspot.com/319150043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://li
david.nales...@gmail.com wrote Tuesday, January 24, 2017 10:57 PM
> Question:
>
> How do I get a backslash in @subsubsubheading{} ?
>
> The literal symbol doesn't show up, and @backslashchar{} displays
> @backslashchar{}
>From memory it's @bs{}.
Trevor
On 2017/01/24 23:32:51, t.daniels_treda.co.uk wrote:
mailto:david.nales...@gmail.com wrote Tuesday, January 24, 2017 10:57
PM
> Question:
>
> How do I get a backslash in @subsubsubheading{} ?
>
> The literal symbol doesn't show up, and @backslashchar{} displays
> @backslashchar{}
From memo
18 matches
Mail list logo
