ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Luca Donetti <donetti@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mtxrun
Date: Sat, 15 Feb 2020 15:38:59 +0100	[thread overview]
Message-ID: <CALkG3Tmm-izKp8yV_mBxECcyKup_7pgDuK+_1As2kWvu4aARfg@mail.gmail.com> (raw)
In-Reply-To: <mailman.0.1581764401.20240.ntg-context@ntg.nl>


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

Thank you Aditya,

> My question is then how
> > do you usually run mtxrun:
> > 1) always writing the full path of the correct executable,
> > 2) avoid putting [lmtx path]/bin in PATH,
> > 3) putting [lmtx path]/bin _after_ [lmtx path]/tex/texmf-linux-64/bin in
> > the PATH
> >
>
> I always follow 2. I don't think that [lmtx path]/bin should ever be in
> the PATH except when updating the installation.
>
> Then I will go with option 2), and report back if I encounter any problem.
If this works well, then it could be useful to change the message shown at
the end of the installation process, as Rudolf already suggested in this
thread.

By the way, you seem to imply that [lmtx path]/bin should be in the PATH
during updates. I didn't know that and I'm sure I've updated several times
without it: I have different environments to be able to switch between
different versions of context (lmtx, the old one, that from texlive...), I
never check which one I'm in before updating lmtx and the installer does
not complain.

LD

[-- Attachment #1.2: Type: text/html, Size: 1423 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:[~2020-02-15 14:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1581764401.20240.ntg-context@ntg.nl>
2020-02-15 14:38 ` Luca Donetti [this message]
2020-02-15 14:48 ` mtxrun Luca Donetti
     [not found] <mailman.474.1581455525.1332.ntg-context@ntg.nl>
2020-02-14 19:59 ` mtxrun Luca Donetti
2020-02-15  4:59   ` mtxrun Aditya Mahajan
2020-02-15  5:40   ` mtxrun Rudolf Bahr
2020-02-15 11:32     ` mtxrun Floris van Manen
2020-02-15 14:57       ` mtxrun Aditya Mahajan
2020-02-10 10:54 mtxrun Rudolf Bahr
2020-02-10 11:06 ` mtxrun Taco Hoekwater
2020-02-10 11:27   ` mtxrun Rudolf Bahr
2020-02-10 12:03 ` mtxrun Rudolf Bahr
2020-02-11 10:56   ` mtxrun Rudolf Bahr
2020-02-11 12:07     ` mtxrun Hans Hagen
2020-02-11 15:23       ` mtxrun Rudolf Bahr
2020-02-11 15:57         ` mtxrun Pablo Rodriguez
2020-02-11 17:26           ` mtxrun Rudolf Bahr
2020-02-11 18:38             ` mtxrun Hans Hagen
2020-02-11 20:41               ` mtxrun Rudolf Bahr
2020-02-11 20:57                 ` mtxrun Aditya Mahajan
2020-02-12  5:44                   ` mtxrun Rudolf Bahr
2020-02-11 18:39             ` mtxrun Aditya Mahajan
2020-02-12  4:41               ` mtxrun Rudolf Bahr
2020-02-12  5:24                 ` mtxrun Aditya Mahajan
2020-02-12 10:05                   ` mtxrun Rudolf Bahr
  -- strict thread matches above, loose matches on Subject: below --
2011-01-23 16:21 MTXrun Herbert Voss
2011-01-23 17:43 ` MTXrun Vedran Miletić
2011-01-23 19:25   ` MTXrun Hans Hagen
2008-06-17 16:49 mtxrun Hans van der Meer
2008-06-17 17:29 ` mtxrun Hans Hagen
2008-06-17 17:34 ` mtxrun Taco Hoekwater
2008-06-17 19:47 ` mtxrun Aditya Mahajan
2008-06-18  8:12   ` mtxrun Hans van der Meer
2008-06-18  9:37     ` mtxrun Hans Hagen
2008-06-18 11:54     ` mtxrun Taco Hoekwater

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=CALkG3Tmm-izKp8yV_mBxECcyKup_7pgDuK+_1As2kWvu4aARfg@mail.gmail.com \
    --to=donetti@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).