[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Doc: improve doc on markup command writing (issue157133)
From: |
Nicolas Sceaux |
Subject: |
Re: Doc: improve doc on markup command writing (issue157133) |
Date: |
Wed, 25 Nov 2009 20:45:14 +0100 |
Le 24 nov. 2009 à 17:51, address@hidden a écrit :
> It would make sense to apply <URL:http://codereview.appspot.com/160048>
> first and make this patch work on top of that.
>
> There may be cases where a separate property-bind like this is useful in
> called routines, and the markup commands from the mentioned patch might
> make use of it for implementing #:properties. However, a separate
> property-bind function can't do the job of entering the properties and
> their defaults into the command reference.
>
> For this reason, it is probably not a good idea to encourage users to
> use a macro like this in markups defined with define-markup-command.
> They would need to be rewritten in order to get the properties mentioned
> in the command reference.
>
> Since the above-mentioned patch does not provide user-level
> documentation, it would make sense to adapt your patch here for
> documenting the functionality provided by the above-mentioned patch of
> mine.
Indeed, actually I "kept it under my arm" for that reason.
Don't hold your breath concerning the review of your patch, I won't be able
to look at it until this week end.
Nicolas
- Re: Doc: improve doc on markup command writing (issue157133), (continued)
Re: Doc: improve doc on markup command writing (issue157133), Ian Hulin, 2009/11/22
Re: Doc: improve doc on markup command writing (issue157133), ian, 2009/11/22
Re: Doc: improve doc on markup command writing (issue157133), nicolas . sceaux, 2009/11/22
Re: Doc: improve doc on markup command writing (issue157133), dak, 2009/11/24
- Re: Doc: improve doc on markup command writing (issue157133),
Nicolas Sceaux <=