From: Patrick Gundlach <pg@levana.de>
Subject: Re: texexec --module problem (was Re: Problem with understanding \doifemptyelse)
Date: Mon, 25 Mar 2002 14:57:08 +0100 [thread overview]
Message-ID: <02032514570800.01383@levana> (raw)
In-Reply-To: <87adswopt0.fsf@inanna.rimspace.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 345 bytes --]
Hallo Daniel,
> Is there any special setup or location that I need to run that command
> from? I tried, because this is an issue that I will soon be looking at,
> and got the following result:
you have to copy the supp-box to the current directory. (And iirc you have
to have the 'cont-nl' format.)
--
Viele Grüße,
Patrick Gundlach
prev parent reply other threads:[~2002-03-25 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 11:26 Problem with understanding \doifemptyelse Gilles Pérez-Lambert
2002-03-23 9:55 ` Hans Hagen
2002-03-25 11:22 ` texexec --module problem (was Re: Problem with understanding\doifemptyelse) Daniel Pittman
2002-03-24 0:30 ` texexec --module problem (was Re: Problem with understanding \doifemptyelse) Hans Hagen
2002-03-25 13:57 ` Patrick Gundlach [this message]
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=02032514570800.01383@levana \
--to=pg@levana.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).