From: vm via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: vm <vm@klankschap.nl>
Subject: Re: [NTG-context] TiKz with LMTX
Date: Mon, 5 Jun 2023 10:35:28 +0200 [thread overview]
Message-ID: <fabd6b21-6ad4-8581-0446-203cbffe0b08@klankschap.nl> (raw)
In-Reply-To: <CAHy-LL9JD5ZjHLUBRogkFM=yGydgqmS=0xWtW8vkwnceZc0org@mail.gmail.com>
On 05/06/2023 07:43, Mikael Sundqvist via ntg-context wrote:
> For whatever it is worth, I just tried to install tikz with
>
> mtxrun --script install-modules --install tikz
>
> and then your example in your first mail did compile here (and gave a
> cross, and that looks right from the source).
did exctly the same steps, but still get the fatal error code 1
Driver file for pgf: pgfsys-luatex.def
! Package pgf Error: Driver file ``pgfsys-luatex.def'' not found..
<macro> \pgfutil@packageerror
#1#2#3->\errhelp {#3}\errmessage {Package #1 Error: #2}
<macro> \pgfutil@IfFileExists
#1#2#3->\openin \pgfutil@inputcheck =#1 \ifeof \pgfutil@inputcheck #3
\relax \else #2\relax \fi \closein \pgfutil@inputcheck
<line 6.1757>
\pgferror{Driver file ``\pgfsysdriver'' not found.}}
.F
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-06-05 8:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1949632129.10002246.1685869873625.ref@mail.yahoo.com>
2023-06-04 9:11 ` Jigé via ntg-context
2023-06-04 14:44 ` Hans Hagen via ntg-context
2023-06-04 15:10 ` Floris van Manen via ntg-context
2023-06-04 16:18 ` Hans Hagen via ntg-context
2023-06-04 21:58 ` Floris van Manen via ntg-context
2023-06-05 5:43 ` Mikael Sundqvist via ntg-context
2023-06-05 8:35 ` vm via ntg-context [this message]
2023-06-05 17:40 ` Aditya Mahajan via ntg-context
2023-06-06 2:32 ` Aditya Mahajan via ntg-context
[not found] <mailman.1302.1685898062.41142.ntg-context@ntg.nl>
2023-06-04 21:04 ` Jigé via ntg-context
[not found] <mailman.1322.1685946193.41142.ntg-context@ntg.nl>
2023-06-05 10:33 ` Jigé via ntg-context
2023-06-05 11:02 ` Floris van Manen via ntg-context
2023-06-05 12:49 ` Carlos via ntg-context
2023-06-05 13:06 ` Floris van Manen via ntg-context
2023-06-05 13:40 ` Carlos via ntg-context
2023-06-05 19:43 ` Carlos via ntg-context
2023-06-05 20:16 ` Carlos via ntg-context
[not found] <mailman.1332.1685970748.41142.ntg-context@ntg.nl>
2023-06-05 14:52 ` Jigé via ntg-context
[not found] <mailman.49.1686219733.1391.ntg-context@ntg.nl>
2023-06-08 18:37 ` Jigé via ntg-context
2023-06-09 3:57 ` Aditya Mahajan via ntg-context
2023-06-09 6:13 ` Hans Hagen via ntg-context
2023-06-09 16:43 ` Aditya Mahajan via ntg-context
2023-06-12 16:49 ` Carlos via ntg-context
2023-06-12 16:59 ` Hans Hagen via ntg-context
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=fabd6b21-6ad4-8581-0446-203cbffe0b08@klankschap.nl \
--to=ntg-context@ntg.nl \
--cc=vm@klankschap.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).