James <pkx1...@gmail.com> writes:
> On 23/12/13 12:26, Urs Liska wrote:
>> Am 23.12.2013 13:02, schrieb David Kastrup:
>>> Urs Liska <u...@openlilylib.org> writes:
>>>
>>>> Am 23.12.2013 12:45, schrieb Urs Liska:
>>>>
>>>>> Attached is an updated patch using @command instead of @code.
>>>>> Rebased patch passes make doc (issues in other subthread solved).
>>>>>
>>>>> Thanks for pushing
>>>>>
>>>>> Urs
>>>>
>>>> Sorry, found an error after reading the sent email: One @code was
>>>> still left. Corrected in attachment.
>>>
>>> And EDITOR is no command. But I'll fix that up myself: it seems silly
>>> chasing you around the bush for that.
>>>
>>
>> Thank you.
>>
>> Is there an authoritative list of texinfo markups to be used?
>
> Do you mean this?
>
> http://lilypond.org/doc/v2.17/Documentation/contributor-big-page.html#texinfo-introduction-and-usage-policy
Missing @env. Unless we get into trouble for
commit 5155adb1fe43e2b166c3101ad48f05d502eef31a
Author: Urs Liska <g...@ursliska.de>
Date: Thu Dec 12 12:06:39 2013 +0100
Issue 3719: CG: Add comment about git-cl editor
git-cl fires either the editor specified by the
EDITOR environment variable or vi if EDITOR isn't defined.
Commit mentions this in the CG
Signed-off-by: David Kastrup <d...@gnu.org>
when GUB-building 2.19.0, we should likely amend the CG accordingly.
According the the NEWS file of makeinfo, @env and @command were
introduced at the same time.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
