From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Some texexec/MP problems
Date: Wed, 18 Sep 2002 11:57:40 +0200 [thread overview]
Message-ID: <20020918115740.531f962d.morawski@gmx.net> (raw)
Hi,
i have some problems with the MP support of texexec:
1. a MP input that has no line-break or whitespace after the "end"
results in mptrace.mp in "endend"
Thus a job 'texexec --mptex myfile.mp' does not
finish correctly. Maybe texexec should add an additional line-break.
2. many of my MP files include more than 100 figures.
I use currently
texexec --pdf --fig=c myfile.[0-9] myfile.[1-9][0-9] myfile.[1-9][0-9][0-9]
to have all figures in _one_ PDF file. But the result ist always the file
texexec.pdf. The texexec option --result=myfile.pdf leads to a missing
myfile.mps. Is this a bug?
3. The strange looking 'myfile.[0-9] myfile.[1-9][0-9] myfile.[1-9][0-9][0-9]'
is necessary to keep the order of the figures, since normally 'myfile.*'
expands in a shell to 'myfile.1 myfile.10 myfile.11 ... myfile.2'
Is it possible to let
'texexec --pdf --fig=c myfile' expand the file-names correctly itself?
Thanks,
Jens
next reply other threads:[~2002-09-18 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 9:57 Jens-Uwe Morawski [this message]
2002-09-18 11:52 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020918115740.531f962d.morawski@gmx.net \
--to=morawski@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).