From: "luigi.scarso" <luigi.scarso@logosrl.it>
Subject: Re: XYpic
Date: Fri, 29 Apr 2005 12:27:39 +0200 [thread overview]
Message-ID: <42720C1B.1070509@logosrl.it> (raw)
In-Reply-To: <4271EE80.5020008@seznam.cz>
Vit, the last things.
After that I consider this topic closed.
>>+ limitation by substance: drawing is mostly done via fonts
Yes, I forget to write it.
>>[XFIG]..Export to context is good news. But still no parametrization
possible :-(
..maybe something to play this summer...
Now for metapost:
shell_escape= f
in texmf.cnf
so \write18 is disabled.
$>texexec --pdf f
No circle; it seems right, because f.log says
systems : randomizer starts with 797065300
mpost -progname=mpost -mem=metafun f-mpgraph
system()...disabled.
$> shell_escape=x ; texutil --purgeall; texexec --pdf f
As before.
$> shell_escape= ; texutil --purgeall; texexec --pdf f
As before.
$> shell_escape=t ; texutil --purgeall; texexec --pdf f
Circle ok; again it's right, f.log says
systems : randomizer starts with 800565448
system(mpost -progname=mpost -mem=metafun f-mpgraph)...executed.
$> shell_escape=f ; texutil --purgeall; texexec --pdf f
Strange:circle again.
I found into texexec.pl
if (($ENV{shell_escape} eq 'f') || ($ENV{SHELL_ESCAPE} eq 'f')) {
$AutoMPRun = 1 ;
}
Hence texexec/texutil has called mpost instead of \write18; it's like
shell_escape=t
(for this task, not in general sense, of course)
Hmm, it's not crystal clear:
shell_escape=f means "shell_escape is False"
shell_escape=t means "shell_escape is True"
but for processing f.tex 'True and False are the same'
$>shell_escape=; texutil --purge; texexec --pdf --automprun f
Circle ok; it seems right, because I force execution of mpost.
Again, many thanks
luigi
next prev parent reply other threads:[~2005-04-29 10:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 15:45 Rif: Re: dotted line for \framed ? Luigi Scarso
2005-04-26 15:35 ` luigi.scarso
2005-04-26 18:24 ` XYpic (was: dotted line for \framed ?) Henning Hraban Ramm
2005-04-27 10:18 ` XYpic Vit Zyka
2005-04-28 8:01 ` XYpic luigi.scarso
2005-04-28 10:42 ` XYpic Vit Zyka
2005-04-28 11:02 ` XYpic luigi.scarso
2005-04-28 22:05 ` XYpic Vit Zyka
2005-04-29 7:08 ` XYpic luigi.scarso
2005-04-29 8:21 ` XYpic Vit Zyka
2005-04-29 10:27 ` luigi.scarso [this message]
2007-04-27 12:46 XYPic Dirard Mikdad
2007-05-01 6:55 ` XYPic luigi scarso
2007-05-01 7:09 ` XYPic luigi scarso
2007-05-01 9:18 ` XYPic Dirard Mikdad
2007-05-01 19:45 ` XYPic luigi scarso
2007-05-02 8:14 ` XYPic Dirard Mikdad
2007-05-02 8:57 ` XYPic luigi scarso
2007-05-02 14:20 ` XYPic Dirard Mikdad
2007-05-02 15:05 ` XYPic luigi scarso
2007-05-02 15:16 ` XYPic Dirard Mikdad
2007-05-02 16:31 ` XYPic luigi scarso
2007-05-03 6:39 ` XYPic luigi scarso
2007-05-04 0:17 ` XYPic luigi scarso
2007-05-04 12:57 ` XYPic Dirard Mikdad
2007-05-04 13:25 ` XYPic luigi scarso
2007-05-14 9:33 ` XYPic luigi scarso
2007-05-15 12:40 ` XYPic Dirard M. Mikdad
2007-04-27 12:49 Xypic Dirard Mikdad
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=42720C1B.1070509@logosrl.it \
--to=luigi.scarso@logosrl.it \
--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).