Hello,
Rasmus ras...@gmx.us writes:
Myles English mylesengl...@gmail.com writes:
1) subtree scope export results differently than buffer scope export
It seems changes set in properties are not registered as changes in the
file cf. 2. Thus, some fields you'd like to get after the LCO file
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Somehow, when you specify it as a property it's not detected
as :inbuffer-signature.
Fixed in b07bd32081db62725af12b185a786aa0d7f99bae. Thank you.
Thanks for fixing this, Nicolas.
Rasmus
--
If you can mix business and politics wonderful
Rasmus writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Somehow, when you specify it as a property it's not detected
as :inbuffer-signature.
Fixed in b07bd32081db62725af12b185a786aa0d7f99bae. Thank you.
Thanks for fixing this, Nicolas.
Yes, and thanks both of you for looking into
Hello,
I have noticed some strange things about koma letter exports (current
git master 329683).
1) subtree scope export results differently than buffer scope export
2) a signature specified in the subtree property does not take
precedence in subtree export
3) superscripts on the dates
Hi Myles,
Thanks for your report.
Myles English mylesengl...@gmail.com writes:
1) subtree scope export results differently than buffer scope export
It seems changes set in properties are not registered as changes in the
file cf. 2. Thus, some fields you'd like to get after the LCO file
