Re: Declarative Diversions - GSoC Project Update 1
Raphael Hertzog <email@example.com> writes:
> Or to use two lines instead of one. And to support multiple entries make
> the different entries separated by an empty line (so that it's possible
> to add supplementary fields in the future shall that be required).
This still doesn't give a completely general solution, although at this
point the number of characters that aren't allowed becomes an edge case.
I don't know if it's worth formalizing an escape procedure so that one
could divert arbitrary filenames (which can contain, for example,
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>