[metapost] verbatimtex bug?
taco at elvenkind.com
Fri Oct 30 18:42:50 CET 2009
Dan Luecking wrote:
> I like the last, since it preserves the EOL (in case that is
> ever significant).
perhaps metapost should be strippinf trailing spaces, but no newlines?
> With no warning that a verbatimtex block inside "..." could cause
> TeX to continue reading for more characters in the filename mymac!
>> There is a --debug switch, which leaves all temporary files in place,
> That --debug switch is good to know, but "mpost --help" doesn't
> display it. The only debugging tool mentioned is: --kpathsea-debug,
> which doesn't seem applicable.
It is a bit of a secret because it clutters the folder quite a bit
(on top of providing extra debug print statements).
>> but I can add an 'mpto' personality to the next release as well (there
>> is a --dvitomp switch already)
> Are there any cases where dvitomp is useful without mpto?
Yes, in texexec. It uses perl/ruby code to extract the text
(because starting a separate mpto for that is quite costly,
and it does more processing than mpto offers, anyway).
In fact, texexec is the reason that there is a --dvitomp at all.
> On an entirely different subject: I was surprised to notice that
> "mpost --help" doesn't display a banner line (i.e., "This is
> MetaPost, version 1.208").
I'll fix that in a future release (but not serious enough for 1.209).
> Also --version and --help can't be combined.
This, I do not care about. If someone wants that changed, send me
a patch :)
More information about the metapost