From: Hans Hagen <j.hagen@xs4all.nl>
To: Vladimir Lomov <lomov.vl@yandex.ru>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Emacs + latest beta
Date: Fri, 24 Aug 2018 16:39:54 +0200 [thread overview]
Message-ID: <b06e37ce-39df-7983-6c48-e80dd05a8963@xs4all.nl> (raw)
In-Reply-To: <20180824134827.GD762@smoon.vl-lomov.ru>
On 8/24/2018 3:48 PM, Vladimir Lomov wrote:
> I don't know why you get "damaged" pdf file (in fact how do you know
> that file is damaged?) but "TEXMFCNF" is special variable that I uses to
> tweak TeX Live configuration for my latex workflow but context
> (standalone and from TL) refuses to work if this variable is set (in
> terminal I do 'unset' while in Emacs I set its value to 'nil' because
> this is identical to "unset" it). The "TEXROOT" variable I found in
> update script, I'm not sure if context requires it to work but IMHO, it
> is harmless. And the last variable "TEXMFCACHE" I use to force context
> to use ~/.cache for "luatex-cache" directory and not "pollute" my home
> directory (without it the "luatex-cache" directory will be created in
> $HOME directory).
context does listen to some of these variables but all lookups are done
independent of kpse, basically you only need to set the path or run
context / mtxrun with a full path, often from an editor
<pathtomtxrun>/mtxrun --script context ....
works ok
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-08-24 14:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 11:05 Fabrice Couvreur
2018-08-22 12:30 ` Vladimir Lomov
2018-08-23 8:48 ` Fabrice Couvreur
2018-08-24 2:20 ` Vladimir Lomov
2018-08-24 10:31 ` Fabrice Couvreur
2018-08-24 13:48 ` Vladimir Lomov
2018-08-24 14:39 ` Hans Hagen [this message]
2018-08-27 3:57 ` Vladimir Lomov
2018-08-24 23:23 ` Fabrice Couvreur
2018-08-27 4:07 ` Vladimir Lomov
2018-08-27 9:51 ` Fabrice Couvreur
2018-08-27 13:47 ` Fabrice Couvreur
2018-08-28 5:57 ` Vladimir Lomov
2018-08-28 9:18 ` Fabrice Couvreur
2018-08-29 2:58 ` Vladimir Lomov
2018-08-29 9:39 ` Fabrice Couvreur
2018-08-29 10:01 ` Fabrice Couvreur
2018-08-29 14:12 ` Vladimir Lomov
2018-08-30 17:13 ` Fabrice Couvreur
2018-08-29 14:01 ` Vladimir Lomov
2018-08-27 14:35 ` Aditya Mahajan
2018-08-27 15:13 ` Fabrice Couvreur
2018-08-23 18:58 ` Wolfgang Schuster
2018-08-24 1:29 ` Vladimir Lomov
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=b06e37ce-39df-7983-6c48-e80dd05a8963@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=lomov.vl@yandex.ru \
--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).