From: Matthew Baker <mbaker@zeus.gmd.de>
Subject: preset bug
Date: Tue, 25 May 1999 14:47:18 +0200 [thread overview]
Message-ID: <Pine.SGI.4.04.9905251445240.169143-100000@sono> (raw)
Forgot to post the errors I get from the preset option, as Hans
requested. Here 'tis:
! Undefined control sequence.
\dodolocatepresetfigurefiles ...nsertionsupported
{#1} {\edef
\@@efcurrentfi...
\next2 #1,->\dodolocatepresetfigurefiles {#1}
\doprocesscommaitem
\nextcommaitem ...mmaitem }\doprocesscommaitem #1,
]\relax \global \advance
\...
\next1 #1,->\dolocatepresetfigurefiles {#1}
\doprocesscommaitem
<argument> eps,
mps,pdf,png,jpg,tif,mov,tex
\nextcommaitem ...ommaitem }\doprocesscommaitem #1
,]\relax \global
\advance ...
...
l.53 ...agedir/id2/img0011][width=17mm,preset=no]}
{}
Since preset wasn't the option I needed annyway, this isn't urgent for me.
Just posting for your info :)
- Matt
--
Dr. Matthew Baker matthew.baker@gmd.de
GMD - FIT.MMK http://fit.gmd.de/hci/pages/matthew.baker.html
reply other threads:[~1999-05-25 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.SGI.4.04.9905251445240.169143-100000@sono \
--to=mbaker@zeus.gmd.de \
--cc=Matthew.Baker@gmd.de \
/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).