From: "Pawel Jackowski na Onet" <jackos1@poczta.onet.pl>
Subject: RME and INI
Date: Mon, 6 Oct 2003 09:18:05 +0200 [thread overview]
Message-ID: <000501c38bda$0895c3f0$0500a8c0@best> (raw)
Hi all!
TEXEXEC documentation and self documented 'texexec.rme' file says that it
should be copied to 'texexec.ini'. First of all; I have two 'texexec.rme' in
TeX tree; first in
...TeX/context/config
the second in
...TeX/context/perltk
Files looks to be identical but and the second location has a priority. But
which location is more convenient for texexec config file?
The second question is WHY I have to copy 'texexec.rme' to 'texexec.ini'? If
I do so and change some settings in 'texexec.ini' and than run
'texexec --verbose', I can see that settings are still taken from
'texexec.rme'. Could You tell me what is the point in copying RME to INI and
when INI file is used instead RME?
Thanks, Pawe/l
next reply other threads:[~2003-10-06 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 7:18 Pawel Jackowski na Onet [this message]
2003-10-06 9:17 ` Patrick Gundlach
2003-10-06 9:37 George N. White III
2003-10-06 11:18 Pawel Jackowski na Onet
2003-10-06 17:06 ` Henning Hraban Ramm
2003-10-06 17:50 ` Pawel Jackowski na Onet
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='000501c38bda$0895c3f0$0500a8c0@best' \
--to=jackos1@poczta.onet.pl \
--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).