ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Set luatex cache directory path
Date: Tue, 6 Apr 2021 11:59:36 -0700	[thread overview]
Message-ID: <CAANrE7qo0Kej2wMghQLpSpr4h43Ezq69qUPcTh-P521B1vhLsw@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2104060330450.5997@nqv-guvaxcnq>


[-- Attachment #1.1: Type: text/plain, Size: 1437 bytes --]

Thanks Aditya.

What do you think of changing the default luatex-cache directory to the
system's temporary directory? Consider:

   - The $HOME directory is sacrosanct (4784 people agree:
   https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1575053)
   - The temp directory is cleared on Linux (Unix?) system reboots; purged
   during regular Windows upkeep
   - The temp directory is writable by default
   - Changing the location requires calling an additional program, which
   isn't obvious (principle of least astonishment)

My text editor invokes ConTeXt like:

    if( TYPESETTER.canRun() ) {
      env.put( "TEXMFCACHE", System.getProperty( "java.io.tmpdir" ) );

      mArgs.add( TYPESETTER.getName() );
      mArgs.add( .. --path .. --purge .. --batch .. --result ..
--environment .. etc. );
      mArgs.add( inputFilename );
    }

The first line ensures that "context" is an executable located in a PATH
directory. The second line attempts to change the luatex-cache directory.
The remaining lines configure the command-line arguments prior to running
ConTeXt.

Fearing flaming wrath from users, an additional mtxrun call is required,
which incurs overhead:

   - Check for mtxrun executable
   - Run mtxrun each time

This would work but feels like a leaky abstraction (i.e., the context
executable should honour TEXMFCACHE without needing to invoke mtxrun
because context creates the luatex-cache directory).

Thoughts?

[-- Attachment #1.2: Type: text/html, Size: 1833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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:[~2021-04-06 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 22:19 Thangalin
2021-04-06  7:31 ` Aditya Mahajan
2021-04-06 18:59   ` Thangalin [this message]
2021-04-06 19:24     ` Aditya Mahajan
2021-04-06 21:06       ` Thangalin
2021-04-10 23:30       ` Thangalin
2021-04-11  9:16         ` Hans Hagen
2021-04-11 21:13           ` Thangalin
2021-04-06 21:38     ` Hans Hagen

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=CAANrE7qo0Kej2wMghQLpSpr4h43Ezq69qUPcTh-P521B1vhLsw@mail.gmail.com \
    --to=thangalin@gmail.com \
    --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).