ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: how to prevent stupid typos?
Date: Wed, 7 Jun 2017 23:01:55 +0200	[thread overview]
Message-ID: <9fd02bac-57af-948c-6296-bed5d354101e@wxs.nl> (raw)
In-Reply-To: <op.y1g8ipctejo439@desktop-mt1m160>

On 6/7/2017 9:02 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
> On Wed, 07 Jun 2017 12:11:14 -0600, Pablo Rodriguez <oinos@gmx.es> wrote:
> 
>>> (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.
> 
> I suppose it wouldn't be too hard for someone with the requisite ability 
> to write a script to pipe and run the check on the argument of each 
> \input in a main file.
> 
> OTOH, \input's can have \input's so it could get unwieldy pretty quick..
> 
> As a matter of workflow, I would just check each \input when editing it, 
> don't see the need to check them all over and over - but maybe you have 
> some huge collaborative project with lots of \inputs frequently changing..
sure it's no big deal to write such a script but in decades of tex i 
never felt the need

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2017-06-07 21:01 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
2017-06-07 19:02         ` Idris Samawi Hamid ادريس سماوي حامد
2017-06-07 20:05           ` Pablo Rodriguez
2017-06-07 21:01           ` Hans Hagen [this message]
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=9fd02bac-57af-948c-6296-bed5d354101e@wxs.nl \
    --to=pragma@wxs.nl \
    --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).