From: Alex Vong <alexvong1995@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Missing native-search-path for texlive
Date: Mon, 30 Nov 2015 21:30:32 +0800 [thread overview]
Message-ID: <CADrxHD8hpy18EJCQTbux-AKR-XUeANEzk5bBSWYGagTkU5_BCg@mail.gmail.com> (raw)
In-Reply-To: <878u5fab63.fsf@gnu.org>
On 30/11/2015, Ludovic Courtès <ludo@gnu.org> wrote:
> Alex Vong <alexvong1995@gmail.com> skribis:
>
>> Yesterday, I try to use compile some document with context, so I
>> install texlive in guix. However, when I run "context --version", I
>> get the following error:
>>
>> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
>>
>> After doing some searching, I find out that the following works:
>>
>> $ TEXMF=`guix build texlive-texmf` context --version
>>
>> What should I add to native-search-path to set the TEXMF variable to
>> the output path?
>
> It ‘TEXMF’ really a search path, or is it rather a variable that should
> point to a single directory?
>
I think it is a search path since both
`TEXMF=/gnu/store/gb4y83bvcpkvdmz0dvi9rp507kbdbr5x-texlive-texmf-2015
context --version` and
`TEXMF=/gnu/store/gb4y83bvcpkvdmz0dvi9rp507kbdbr5x-texlive-texmf-2015/share
context --version` works. But otherwise, I don't know how environment
variables in texlive works. I see there are other environmental
variables as well. For instance, TEXINPUTS, TEXMFLOCAL and TEXMFHOME.
But only TEXMF and TEXMFHOME works.
> If the issue is limited to the ‘context’ program, then we may be better
> off wrapping ‘context’ such that ‘TEXMF’ is always set appropriately.
>
> Thoughts? Andreas?
>
> Ludo’.
>
next prev parent reply other threads:[~2015-11-30 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 1:41 Missing native-search-path for texlive Alex Vong
2015-11-30 13:07 ` Ludovic Courtès
2015-11-30 13:30 ` Alex Vong [this message]
2015-11-30 14:20 ` Andreas Enge
2015-11-30 16:37 ` Alex Vong
2015-12-30 10:32 ` Andreas Enge
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADrxHD8hpy18EJCQTbux-AKR-XUeANEzk5bBSWYGagTkU5_BCg@mail.gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).