Line ending translation extension

Greg Ward greg-hg at gerg.ca
Thu Sep 10 20:47:45 CDT 2009


On Thu, Sep 10, 2009 at 7:43 PM, Martin Geisler <mg at lazybytes.net> wrote:
> I was looking at the keyword extension tonight and it occured to me that
> it does everything we want: it can expand and shring keywords (convert
> to/from native format). It overrides lots of commands to ensure that
> this is done correctly.
>
> We're currently trying to make do with the encode/decode filters -- I
> wonder if this is because the keyword extension makes things more
> complicated that they are, or if we will also need to do this?

Interesting.  I was following the Bazaar list back when they added EOL
translation, and it sounded like the real work was implementing a
filtering framework.  At any rate, keyword expansion and EOL
translation both depended on the filtering framework.  I wonder if
it's worth examining what 'keywords' does and somehow promoting that
to first class: e.g. implement some interface (or provide a bunch of
callables to be more Mercurial-esque) to filter content.

Greg


More information about the Mercurial-devel mailing list