From: nico <nicolas.marsgui@libertysurf.fr>
Subject: No metapost compilation on files named file.001.tex
Date: Thu, 20 Apr 2006 00:14:35 +0200 [thread overview]
Message-ID: <ops79z2lbe9niby6@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
Hello,
There's something wrong in using (old)texexec/metapost on an input file
named file.001.tex (I guess that 001 could be any number): the mp graphic
is not generated. If I change file.001.tex to file.tex, it works ok.
I attach the test file used if it can be useful.
Regards,
BG
[-- Attachment #2: try2.001.tex --]
[-- Type: application/x-tex, Size: 850 bytes --]
[-- Attachment #3: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2006-04-19 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 22:14 nico [this message]
2006-04-20 5:34 ` Thomas A. Schmitz
2006-04-20 7:57 ` Hans Hagen
2006-04-20 19:15 ` nico
2006-04-20 20:12 ` 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=ops79z2lbe9niby6@localhost \
--to=nicolas.marsgui@libertysurf.fr \
--cc=ntg-context@ntg.nl \
/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).