Peter Dyballa writes:
> PostScript debugging makes it necessary to know exactly what is fed
> into gs in its own process environment. This information is not
> delivered.
This is not a problem at all. If you are interested in what is sent
to gs, there is a simple trick: Just temporarily replace the gs
binary by a script which redirects its input to a file.
Similarly, if you want to know with which arguments gv is invoked,
replace gs by a script like
#!/bin/sh
echo "$@"
and run gv. And if you are debugging PostScript quite often, maybe
my little script
http://ms25.ath.cx/stackdump.ps
is quite convenient. It defines the procedure ?? which prints the
content of the stack to screen. Try
gs -q -dBATCH -dNODISPLAY stackdump.ps myfile.ps
where myfile.ps contains, for example:
(hello) 1 2 ?? mul 3 4 ??
Regards,
Reinhard
--
----------------------------------------------------------------------------
Reinhard Kotucha Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover mailto:[EMAIL PROTECTED]
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------
_______________________________________________
bug-auctex mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-auctex
