From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: [DKIM] Re: [DKIM] circuitikz module seems broken
Date: Fri, 3 Dec 2021 09:47:12 -0500 (EST) [thread overview]
Message-ID: <nycvar.YAK.7.78.908.2112030940300.2024218@nqv-guvaxcnq> (raw)
In-Reply-To: <a25e26e8-f1ef-b7a2-9bab-fe3e771bfa42@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Fri, 3 Dec 2021, Hans Hagen via ntg-context wrote:
> On 12/3/2021 10:49 AM, Hans Hagen via ntg-context wrote:
>
> >> I’ve been struggeling with the circuitikz module since my upgrade to
> >> LMTX.
> btw, We can have more 'catches' in the loader (t) module if needed. In
> any case, also check if things work with mkiv.
I tested the example on mkiv, I got error that dipchip and fliflop JK are not defined. The file compiles if I comment those out. But in LMTX, I also get a "missing semicolon" error. There is also this warning, which may have something to do with what is going wrong:
system > module wrapping error in 'tikz'
The error appears to be related to keyword arguments. The following example works:
\usemodule[circuitikz]
\starttext
\startcircuitikz
\draw (0,2) to[I] (2,2) ;
\stopcircuitikz
\stoptext
But this does not:
\usemodule[circuitikz]
\starttext
\startcircuitikz
\draw (0,2) to[I=1] (2,2) ;
\stopcircuitikz
\stoptext
Aditya
[-- 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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-12-03 14:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 7:54 Jan-Erik Hägglöf via ntg-context
2021-12-03 9:49 ` [DKIM] " Hans Hagen via ntg-context
2021-12-03 13:54 ` [DKIM] " Hans Hagen via ntg-context
2021-12-03 14:17 ` skrantajanneman via ntg-context
2021-12-03 14:40 ` [DKIM] " Hans Hagen via ntg-context
2021-12-03 14:47 ` Aditya Mahajan via ntg-context [this message]
2021-12-03 18:16 ` Hans Hagen via ntg-context
2021-12-03 22:39 ` Jan-Erik Hägglöf via ntg-context
2021-12-03 23:27 ` Aditya Mahajan via ntg-context
2021-12-04 9:05 ` Henning Hraban Ramm via ntg-context
2021-12-04 21:37 ` Jan-Erik Hägglöf via ntg-context
2021-12-05 15:35 ` [DKIM] " Hans Hagen via ntg-context
2021-12-05 20:45 ` [DKIM] " Jan-Erik Hägglöf via ntg-context
2021-12-06 6:54 ` [DKIM] " Aditya Mahajan via ntg-context
2021-12-06 9:02 ` Aditya Mahajan via ntg-context
2021-12-06 17:39 ` Aditya Mahajan via ntg-context
2021-12-06 19:30 ` Hans Hagen via ntg-context
2021-12-06 20:49 ` Jan-Erik Hägglöf via ntg-context
2021-12-07 8:48 ` [DKIM] " Hans Hagen via ntg-context
2021-12-08 5:30 ` Aditya Mahajan via ntg-context
2021-12-13 20:08 ` Aditya Mahajan via ntg-context
2021-12-13 20:14 ` Jan-Erik Hägglöf via ntg-context
2021-12-13 22:35 ` Jan-Erik Hägglöf via ntg-context
2021-12-13 23:54 ` Hans Hagen via ntg-context
2021-12-14 3:57 ` Aditya Mahajan via ntg-context
2021-12-14 13:14 ` Jan-Erik Hägglöf 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=nycvar.YAK.7.78.908.2112030940300.2024218@nqv-guvaxcnq \
--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).