From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Very strange error:
Date: Tue, 15 Aug 2023 16:45:27 +0200 (CEST) [thread overview]
Message-ID: <8q61484p-207o-25sr-n28p-oo5n29870n66@hzvpu.rqh> (raw)
In-Reply-To: <20230814232601.cf18abdffcb5f5d7f314befb@posteo.net>
On Mon, 14 Aug 2023, Xavier B. wrote:
> > Can you show the text (and commands) which appears on line 540 (plus a
> > few lines before/after line 540) of your document.
> >
> I attach the dev.log and dev-error.log. Is it enough?
You should show a *complete* context source document that generates the error. See
https://tex.meta.stackexchange.com/questions/228/ive-just-been-asked-to-write-a-minimal-working-example-mwe-what-is-that
(Most of the advice here is latex specific, but the idea is the same for context).
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-08-15 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 15:41 [NTG-context] " Xavier B.
2023-08-14 15:49 ` [NTG-context] " Wolfgang Schuster
2023-08-14 21:26 ` Xavier B.
2023-08-15 14:45 ` Aditya Mahajan [this message]
2023-08-14 16:42 ` Rik Kabel
2023-08-14 16:49 ` Rik Kabel
2023-08-14 17:07 ` Wolfgang Schuster
2023-08-14 21:50 ` Xavier B.
2023-08-14 22:03 ` Xavier B.
2023-08-15 3:55 ` Wolfgang Schuster
2023-08-14 21:24 ` Xavier B.
2023-08-14 22:25 ` Hans Hagen via ntg-context
2023-08-15 18:58 ` Wolfgang Schuster
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=8q61484p-207o-25sr-n28p-oo5n29870n66@hzvpu.rqh \
--to=adityam@umich.edu \
--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).