Thanks Marc.
https://codereview.appspot.com/120480043/diff/11/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/120480043/diff/11/Documentation/notation/input.itely#newcode2747
Documentation/notation/input.itely:2747: @emp
:) Sorry. Some more tightening of the text.
https://codereview.appspot.com/145490043/diff/1/Documentation/notation/fretted-strings.itely
File Documentation/notation/fretted-strings.itely (right):
https://codereview.appspot.com/145490043/diff/1/Documentation/notation/fretted-strings.itely#newcod
Welcome back Valentine!
P.S. don't forget to update the google tracker (if not using git-cl) -
Patch-New means the patch gets automatic testing.
https://codereview.appspot.com/145490043/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/14
On 14-09-28 04:43 PM, v.villen...@gmail.com wrote:
Reviewers: ,
Message:
Greetings everybody,
here's a thought: the shorthand syntax for string numbers is so useful
that it shouldn't be limited to fretted strings, but could also come
handy for unfretted strings notation. This is the less dirty
Reviewers: ,
Message:
Greetings everybody,
here's a thought: the shorthand syntax for string numbers is so useful
that it shouldn't be limited to fretted strings, but could also come
handy for unfretted strings notation. This is the less dirty way I
could find of making that happen.
(Sidebar:
https://codereview.appspot.com/120480043/diff/11/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/120480043/diff/11/Documentation/notation/input.itely#newcode2747
Documentation/notation/input.itely:2747: @emph{two} @code{\
On 2014/09/28 06:49:08, dak wrote:
On 2014/09/28 06:33:12, dak wrote:
> Uh, to answer your question: easy way: probably not really. But if
you make
an
> extra issue "Make \tweak work on \time", your current code will
magically
create
> the warning pointing to the source as a side effect.
Urs, you wrote Sunday, September 28, 2014 10:38 AM
> Am 28.09.2014 11:36, schrieb Trevor Daniels:
>>
>> Most of the engravers are written in C++ and each is a separate
>> file in the lily/ directory. There's a little above engravers here:
>>
>> http://www.lilypond.org/doc/v2.19/Documentation/co
James writes:
> On 28/09/14 10:44, David Kastrup wrote:
>> Urs Liska writes:
>>
>>> Hi devs,
>>>
>>> sorry for the uninformed question, but I don't seem to be able to find
>>> an answer in the CG or in the source directory.
>>>
>>> If I have a new Scheme engraver that I'd like to suggest to be
Am 28.09.2014 11:44, schrieb David Kastrup:
Urs Liska writes:
Hi devs,
sorry for the uninformed question, but I don't seem to be able to find
an answer in the CG or in the source directory.
If I have a new Scheme engraver that I'd like to suggest to be added,
where would I look for a place t
On 28/09/14 10:44, David Kastrup wrote:
> Urs Liska writes:
>
>> Hi devs,
>>
>> sorry for the uninformed question, but I don't seem to be able to find
>> an answer in the CG or in the source directory.
>>
>> If I have a new Scheme engraver that I'd like to suggest to be added,
>> where would I lo
Urs Liska writes:
> Hi devs,
>
> sorry for the uninformed question, but I don't seem to be able to find
> an answer in the CG or in the source directory.
>
> If I have a new Scheme engraver that I'd like to suggest to be added,
> where would I look for a place to add it to?
> Is there a file (or
Am 28.09.2014 11:36, schrieb Trevor Daniels:
Urs, you wrote Sunday, September 28, 2014 10:07 AM
sorry for the uninformed question, but I don't seem to be able to find
an answer in the CG or in the source directory.
If I have a new Scheme engraver that I'd like to suggest to be added,
where wo
Hi devs,
sorry for the uninformed question, but I don't seem to be able to find
an answer in the CG or in the source directory.
If I have a new Scheme engraver that I'd like to suggest to be added,
where would I look for a place to add it to?
Is there a file (or a set of files grouped by topi
14 matches
Mail list logo