[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tracker 1686 - Process question - separate Tracker Issues or handle
From: |
Ian Hulin |
Subject: |
Re: Tracker 1686 - Process question - separate Tracker Issues or handle patches as part of T1686? |
Date: |
Tue, 08 Nov 2011 13:24:02 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 |
Hi David
On 08/11/11 08:45, David Kastrup wrote:
> Ian Hulin <address@hidden> writes:
>
>> o Move all the markup macros and markup definition procedures to a new
>> (scm markup-facility-defs) module (this is the artist formerly known
>> markup-macros.scm and the remaining code in markup.scm)
>> - add (use-modules (scm markup-facility-defs)) to all the scheme
>> files that use the define-markup-command,
>> (especially define-markup-commands.scm).
>
> Will this affect user-defined markup commands in the document as well?
>
Nice catch! The sections on defining markup and markup-list commands in
/Extending/ will need updating. (It will need quite an extensive
overhaul for Guile V2, as well.)
Cheers,
Ian
Re: Tracker 1686 - Process question - separate Tracker Issues or handle patches as part of T1686?, David Kastrup, 2011/11/08
- Re: Tracker 1686 - Process question - separate Tracker Issues or handle patches as part of T1686?,
Ian Hulin <=