From: "Patrick Gundlach" <pg@levana.de>
Subject: Re: compile problems
Date: 27 Jun 2004 20:51:11 +0200 [thread overview]
Message-ID: <m2d63kq1gg.fsf@levana.de> (raw)
In-Reply-To: <opr99nf4pxu9mfh0@lamar.colostate.edu> (Idris Samawi Hamid's message of "Sun, 27 Jun 2004 12:39:30 -0600")
Hello again,
>> There are no *.ini files in the latest beta, but 2 *.rme files;
>> which one of them should be modified (or both)?
[...]
> I hope that in the next beta something can be done to obliviate the
> need to edit the rme files!
Just put the ini file in a place that doesn't get erased on an update.
Patrick
--
texshow-web: http://members.ping.de:8061
ConTeXt wiki: http://members.ping.de:8062
next prev parent reply other threads:[~2004-06-27 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 19:01 Idris Samawi Hamid
2004-06-27 7:51 ` Giuseppe Bilotta
2004-06-27 17:43 ` Idris Samawi Hamid
2004-06-27 17:55 ` Re[2]: " Giuseppe Bilotta
2004-06-27 18:21 ` Idris Samawi Hamid
2004-06-27 18:27 ` Idris Samawi Hamid
2004-06-27 18:37 ` Patrick Gundlach
2004-06-27 18:39 ` Re[2]: " Idris Samawi Hamid
2004-06-27 18:51 ` Patrick Gundlach [this message]
2004-06-27 19:00 ` Idris Samawi Hamid
2004-06-28 8:08 ` Hans Hagen
2004-06-28 9:07 ` Re[2]: " Giuseppe Bilotta
2004-06-28 13:05 ` Olaf Weber
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=m2d63kq1gg.fsf@levana.de \
--to=pg@levana.de \
--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).