From: "Johannes Hüsing" <tmi0m0@spi.power.uni-essen.de>
Subject: Re: format file, where? ct'd
Date: Tue, 31 Oct 2000 12:25:53 +0100 [thread overview]
Message-ID: <20001031122553.27762@spi.power.uni-essen.de> (raw)
In-Reply-To: <3.0.6.32.20001031094343.01221470@pop.wxs.nl>; from Hans Hagen on Tue, Oct 31, 2000 at 09:43:43AM +0100
On Tue 2000-10-31 (09:43), Hans Hagen wrote:
> At 08:42 PM 10/30/00 +0100, Johannes Hüsing wrote:
> >Hans and all,
> >I have created files named cont-{de,nl,uk,en}.ini and filled them with the
> >appropriate input and endinput statements.
> >
> >No effect on the behaviour of texexec or fmtutil. It is still in want of
> >cont-en info or cont---alone info, depending on if I enter texexec --make or
> >texexec --make --alone.
>
> Did you run mktexlsr? [needed when you add files to the texmf tree]
Yes, that is to say, I'm used to running texhash which apparently
does the same.
Groetjes
Johannes
prev parent reply other threads:[~2000-10-31 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 19:42 Johannes Hüsing
2000-10-31 8:43 ` Hans Hagen
2000-10-31 11:25 ` Johannes Hüsing [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=20001031122553.27762@spi.power.uni-essen.de \
--to=tmi0m0@spi.power.uni-essen.de \
--cc=johannes.huesing@uni-essen.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).