Re: difference betwwen \pad-around and \pad-markup?

[Carl Sorensen]

On 8/12/09 5:54 PM, "Graham Percival" <address@hidden> wrote:

> On Wed, Aug 12, 2009 at 05:43:39PM -0600, Carl Sorensen wrote:
>> 
>> Also, we need to recognize that the first commit after running convert-ly on
>> the docs and the snippets will result in changes to every version statement.
> 
> Yes.  Now, we could just *hope* that there's only one convert-ly
> update for each version, but that would be silly.  What about
> adding:
>    convert-ly --from "2.13.3" ...
> (where 2.13.3 is the previous downloadable version)
> 
> to the above commands?
> 

It appears that when I run convert-ly  on the regtests, it updates the
version number on *every* regtest, not just those whose syntax has changed.
So I have hundreds of files in my commit.

That's why I wanted to have part of the job of releasing a development
version be to
A) bump VERSION
B) run convert-ly on the Docs, the snippets, and the regtests.

Once we have all of the versions up to the current devel version, changes
will be made only when the syntax changes in the file.

A related problem is that when I run convert-ly as

find input/regression *.ly | xargs convert-ly -e --from "2.13.3"

it does a convert-ly on all the files in input/regression/out/* and
input/regression/out-www/*.  I don't want to mess with those files; they're
created by the build system.

I've been trying to figure out how to get find to ignore any subdirectories
called out/ or out-*/, but haven't been able to figure it out yet.  Any help
would be appreciated.

Thanks,

Carl






>> Maybe we need to make sure that part of the release of a new development
>> version is to:
>> 
>> A. Bump VERSION
>> B. Run convert-ly (there won't be any rules, but it will change all the
>> version statements, so once convert-ly is run on a new snippet and changes
>> it, the proper changes will be tracked in git.
> 
> convert-ly only changes version statements if there's a syntax
> change, so this would do nothing.
> 
> 
>> Back to update procedure:
>> 
>> 3) If convert rule *is* NOT_SMART,
>> A) Manually copy all snippets resulting in NOT_SMART conversion to
>> B) Manually update all of these snippets:
>> C) Run scripts/auxiliar/makelsr.py
> 
> Yes, as far as it goes -- I didn't keep track of the numerous
> discussions about translated docs.  What happens to those?
> 
> 
> Cheers,
> - Graham