ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Aditya Mahajan <adityam@umich.edu>
Subject: Re: lmtx doesn't search texmf-local
Date: Wed, 3 Apr 2019 00:32:38 +0200	[thread overview]
Message-ID: <9b9b1cd8-6103-bf0b-1b38-a9eab92696c0@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.76.44.1904021746410.30496@ervasbepr.pvz.zptvyy.pn>

On 4/2/2019 11:49 PM, Aditya Mahajan wrote:
> On Wed, 3 Apr 2019, Henri Menke wrote:
> 
>> On 3/04/19 10:19 AM, Taco Hoekwater wrote:
>>> My guess: drop the '/opt/context-lmtx/bin' from your PATH.
>>
>> That works, thank you.  Then install.sh has to be adjusted because it 
>> told me to
>>
>>    export 
>> PATH=/opt/context-lmtx/tex/texmf-linux-64/bin:/opt/context-lmtx/bin:/opt/context-lmtx/tex/texmf-linux-64/bin:... 
>>
> 
> The install.sh needs to have the /opt/context-lmtx/bin in the path 
> because the install script (might) need the latest binary to work. The 
> directory structure is almost similar to context standalone. So, I 
> simply created a simple setuptex file to ease munging of paths.
nothing fundamental has changed in that department (nor will change 
drastically unless there is a good reason for it) .. if things don't 
work as expected i'll fix it of course

let me stress that, although there are changes (or pending ones) onder 
the hood, most components of context will just stay as they are (why 
reinvent wheels that turn smoothly)

for instance, font related code is also supposed to work with plain 
which in turn means work with luatex ... the same is true for file 
handling, process management etc ...

lmtx is supposed to be a drop in that context knows how to deal with, 
but with a whole lot of benefits (like running a bit better on Alan's 
refrigerator ... in fact, my thermostat/heating system really does run 
on luatex as does other domotica stuff)

(believe it or not but i occasionally do test lmtx in a small setup 
because computers don't get faster, virtualization has smaller setups, 
energy consumption matters, etc. ... hobyism of course)

one can alway swonder if we keep some ideas in our sleeves .. after all, 
there need to be progress occasionally ...

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
___________________________________________________________________________________

      reply	other threads:[~2019-04-02 22:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 20:46 Henri Menke
2019-04-02 21:02 ` Hans Hagen
2019-04-02 21:19   ` Taco Hoekwater
2019-04-02 21:21     ` Henri Menke
2019-04-02 21:49       ` Aditya Mahajan
2019-04-02 22:32         ` Hans Hagen [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=9b9b1cd8-6103-bf0b-1b38-a9eab92696c0@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=adityam@umich.edu \
    --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).