2013/4/10 David Kastrup
>
> Janek Warchoł writes:
> > Of course not! But when i'm editing Wikipedia, i have syntax buttons
> > next to me, and i can preview changes without waiting more than a few
> > seconds.
>
> Maybe you should try using Emacs as an editor. It has menus and buttons
> for wri
Hi all,
2013/4/5 Janek Warchoł
> Hi,
>
> The name "OctavateEight" doesn't have any sense - it doesn't show that
> this grob is related to the clef, and anyway the clef can be
> "transposed" by any amount, not just an octave.
> I suggest to rename this grob to ClefTransposition or something
> si
LGTM,
amended with Ian's comment about _double_ angle brackets.
https://codereview.appspot.com/8581044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Maybe say "double angle brackets" for '<< ... >>' blocks, as simply
"angle brackets" implies '< ... >'
https://codereview.appspot.com/8581044/diff/1/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):
https://codereview.appspot.com/8581044/diff/1/Documentation/usag
2013/4/10 Fan Ziye :
> Dear list,
>
> Hi, I introduced myself to you several weeks ago – a fourth-year
> undergraduate student of EECS wanting to be involved in lilypond’s
> developing. And then Mike told me to read the CG. (Thank you very much!).
>
> But sorry for my absence in recent time, I was
On 10 avr. 2013, at 16:13, "Fan Ziye" wrote:
> Dear list,
>
> Hi, I introduced myself to you several weeks ago – a fourth-year
> undergraduate student of EECS wanting to be involved in lilypond’s
> developing. And then Mike told me to read the CG. (Thank you very much!).
> But sorry for my a
Dear list,
Hi, I introduced myself to you several weeks ago – a fourth-year undergraduate
student of EECS wanting to be involved in lilypond’s developing. And then Mike
told me to read the CG. (Thank you very much!).
But sorry for my absence in recent time, I was busy with my graduate projec
> But when i'm editing Wikipedia, i have syntax buttons next to me,
> and i can preview changes without waiting more than a few seconds.
As David has said, makeinfo called via `make' does the syntax checks
for you, and with the `info' program (or the Emacs editor) you can see
the resulting change
Janek Warchoł writes:
> 2013/4/10 Werner LEMBERG :
>>
>>> that's why i don't like writing docs - i don't remember the syntax
>>> :)
>>
>> Tsk tsk tsk.
>>
>>> I wonder if it would be easier if we were using some wiki - this was
>>> a simple doc addition and it took me about an hour to do all the
>
2013/4/10 Werner LEMBERG :
>
>> that's why i don't like writing docs - i don't remember the syntax
>> :)
>
> Tsk tsk tsk.
>
>> I wonder if it would be easier if we were using some wiki - this was
>> a simple doc addition and it took me about an hour to do all the
>> maintenance...
>
> And you think
> that's why i don't like writing docs - i don't remember the syntax
> :)
Tsk tsk tsk.
> I wonder if it would be easier if we were using some wiki - this was
> a simple doc addition and it took me about an hour to do all the
> maintenance...
And you think that wrong Wiki syntax (which you event
2013/4/10 :
> On 2013/04/10 10:45:29, janek wrote:
>>
>> bang.
>> that's why i don't like writing docs - i don't remember the syntax :)
>
> You _are_ aware that a simple "make" will check the Texinfo syntax of
> the docs, just not the syntax of any embedded LilyPond example?
No, i wasn't - silly
On 2013/04/10 10:45:29, janek wrote:
bang.
that's why i don't like writing docs - i don't remember the syntax :)
I wonder if it would be easier if we were using some wiki - this was a
simple
doc addition and it took me about an hour to do all the maintenance...
You _are_ aware that a simpl
bang.
that's why i don't like writing docs - i don't remember the syntax :)
I wonder if it would be easier if we were using some wiki - this was a
simple doc addition and it took me about an hour to do all the
maintenance...
https://codereview.appspot.com/8384043/diff/23001/Documentation/notati
nearly there
https://codereview.appspot.com/8384043/diff/23001/Documentation/notation/vocal.itely
File Documentation/notation/vocal.itely (right):
https://codereview.appspot.com/8384043/diff/23001/Documentation/notation/vocal.itely#newcode1641
Documentation/notation/vocal.itely:1641: @emph {Tem
On 2013/04/10 07:06:47, dak wrote:
On 2013/04/10 06:50:59, janek wrote:
> Hmm, so i'd have to ref "Single-staff polyphony"
> which is a @node?
Texinfo comes with a manual. You can either reference
a @node or an @anchor.
Indeed, there's something about this in
http://www.lilypond.org/doc/v2.
On 2013/04/10 07:29:26, dak wrote:
Again, I don't know what the standards would be. The non-centered
rests look
bad particularly in tablature, but are also weird in two-line drum
staffs.
Neither am I. I was flying this by "least ugly" according to my
subjective impression.
For ancient
On 2013/04/10 06:50:59, janek wrote:
Hmm, so i'd have to ref "Single-staff polyphony" which is a @node?
Yes. In this situation we usually write something like,
"See Temporary polyphonic passages in Single-staff polyphony"
(with correct texinfo markup of course).
The different headings and th
On 2013/04/10 05:47:20, Keith wrote:
You changed more than necessary to fix the reported bug. This is good
because
finally voiced r1-style whole rests are in the correct positions
(which I
confirmed with Ted Ross' book just to be careful).
More by coincidence than by design. That was like
On 2013/04/10 06:50:59, janek wrote:
https://codereview.appspot.com/8384043/diff/15001/Documentation/notation/vocal.itely
File Documentation/notation/vocal.itely (right):
https://codereview.appspot.com/8384043/diff/15001/Documentation/notation/vocal.itely#newcode1641
Documentation/notation/v
20 matches
Mail list logo
