From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: how to prevent stupid typos?
Date: Wed, 7 Jun 2017 20:11:14 +0200 [thread overview]
Message-ID: <18c9533d-5c64-d830-3d1b-d02d10c388f6@gmx.es> (raw)
In-Reply-To: <f3966913-6320-95ac-06e0-0e9287bfa84c@wxs.nl>
On 06/07/2017 10:09 AM, Hans Hagen wrote:
> On 6/7/2017 7:02 AM, Pablo Rodriguez wrote:
>> [...]
>> If I runt "mtxrunjit --autogenerate --script check b.tex", I get the
>> following message:
>>
>> no error
>>
>> Is there no way to check also the files loaded by the main source?
>
> i just run that command from the editor (configured under a key) so i
> can use it when editing a file
Hans,
I have just discovered the command (thanks to the kind help of Idris),
so I still have to experiment with it.
First of all, many thanks for the command (method, or whatever it should
be called). It is really useful.
In my real-world issue, the tool it spotted my mistake (a non-closed
\startnotmode nested in \startmode and followed by another \startmode).
My previous reply came before having used the checking method.
> (but i have to admit that i normally just run files and redo after
> fixing an error, running is fast enough)
My question here isn’t about speed. If a source may load twenty source
files and it actually loads five source files, the problem is having to
check the files individually.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2017-06-07 18:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 20:02 Pablo Rodriguez
2017-06-06 20:56 ` Idris Samawi Hamid ادريس سماوي حامد
2017-06-07 5:02 ` Pablo Rodriguez
2017-06-07 8:09 ` Hans Hagen
2017-06-07 18:11 ` Pablo Rodriguez [this message]
2017-06-07 19:02 ` Idris Samawi Hamid ادريس سماوي حامد
2017-06-07 20:05 ` Pablo Rodriguez
2017-06-07 21:01 ` Hans Hagen
2017-06-08 4:05 ` Pablo Rodriguez
2017-06-08 4:39 ` Brian Ballsun-Stanton
2017-06-07 19:08 ` Hans Hagen
2017-06-07 20:08 ` Pablo Rodriguez
2017-06-07 20:16 ` Idris Samawi Hamid ادريس سماوي حامد
2017-06-07 20:33 ` Pablo Rodriguez
2017-06-07 20:45 ` Idris Samawi Hamid ادريس سماوي حامد
2017-06-07 18:55 ` Idris Samawi Hamid ادريس سماوي حامد
2017-06-06 20:57 ` Alan BRASLAU
2017-06-07 5:04 ` Pablo Rodriguez
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=18c9533d-5c64-d830-3d1b-d02d10c388f6@gmx.es \
--to=oinos@gmx.es \
--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).