From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: [NTG-context] tikz + lmtx
Date: Fri, 28 Apr 2023 10:26:22 -0400 (EDT) [thread overview]
Message-ID: <42980n8p-9267-5p80-1rp9-41s9p6sn22n9@hzvpu.rqh> (raw)
In-Reply-To: <1uwaxaok179im.dlg@nililand.de>
On Fri, 28 Apr 2023, Ulrike Fischer via ntg-context wrote:
> Am Fri, 28 Apr 2023 01:01:23 -0400 (EDT) schrieb Aditya Mahajan via
> ntg-context:
>
> > Circuitikz still doesn't work. Even loading the module fails.
>
> It works for me on texlive 2023 with your new module file.
Thanks for testing. I'll double check what was going wrong with my circuitikz tests.
Aditya
___________________________________________________________________________________
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-04-28 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 4:08 Aditya Mahajan via ntg-context
2023-04-28 5:01 ` Aditya Mahajan via ntg-context
2023-04-28 13:22 ` Ulrike Fischer via ntg-context
2023-04-28 14:08 ` Gavin via ntg-context
2023-04-28 14:25 ` Aditya Mahajan via ntg-context
2023-04-28 16:42 ` Floris van Manen via ntg-context
2023-04-28 21:38 ` Aditya Mahajan via ntg-context
2023-04-28 14:26 ` Aditya Mahajan via ntg-context [this message]
2023-05-02 5:49 ` Aditya Mahajan via ntg-context
2023-05-04 14:45 ` Hans Hagen via ntg-context
2023-05-04 21:12 ` Aditya Mahajan via ntg-context
2023-05-04 21:22 ` 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=42980n8p-9267-5p80-1rp9-41s9p6sn22n9@hzvpu.rqh \
--to=ntg-context@ntg.nl \
--cc=adityam@umich.edu \
/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).