ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: RFE: Better error messages for \usemodule
Date: Sun, 17 Jul 2005 20:27:29 +0200	[thread overview]
Message-ID: <42DAA311.4020408@wxs.nl> (raw)
In-Reply-To: <4.3.1.2.20050716234357.01ce5eb0@cits1.stanford.edu>

Brooks Moses wrote:

> At 11:16 PM 7/16/2005, you wrote:
>
>> Brooks Moses wrote:
>>
>>> After scratching my head over "no macros found in module mymodule", 
>>> I decided to try replacing the line with "\input{t-mymodule}".
>>
>>
>>
>>> This produced the very cryptic result of a "I can't find the file 
>>> 't-mymodule'.  Please type another filename:" error.  However, 
>>> simply using "t-mymodule" as a replacement filename worked fine.
>>
>>
>> The \input with braces is latex-ese. The TeX primitive is
>>   \input t-mymodule
>> and that would have worked.
>
>
> Ah, ok.  I hadn't realized those were different!

There are a few file reading macros, for instance:

\readfile {yourfile.tex} {\message{OK}} {\message{BAD NEWS}}

supp-fil.tex shows a few (global loading, local loading, recursive 
loading, etc) ans in core-fil there are some macros to load files with 
knowledge of system paths and such

>> However, as of ConTeXt release 2005.05.25, the original \usemodule
>> would also have worked: the automatic filename truncation was removed
>> in that version.
>
>
> Good to know; it _did_ seem like something that really was likely to 
> be more of an annoyance than a useful thing.

it was useful in the days that 8+3 filenames were the rule (msdos but 
also cdroms demanded it) and that the tex binaries were not able to 
handle truncated names well

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2005-07-17 18:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17  0:13 Brooks Moses
2005-07-17  6:16 ` Taco Hoekwater
2005-07-17  6:45   ` Brooks Moses
2005-07-17 18:27     ` Hans Hagen [this message]
2005-07-17  6:16 ` Taco Hoekwater
2005-07-17  6:32   ` Taco Hoekwater
2005-07-17 14:13     ` another problem with textbackground Martin Kolarík
2005-07-17 14:14     ` Martin Kolarík
2005-07-17 21:43       ` Hans Hagen
2005-07-17  6:17 ` RFE: Better error messages for \usemodule Taco Hoekwater

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=42DAA311.4020408@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).