From: Marco Patzer via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco Patzer <lists@homerow.info>
Subject: Re: \typefile not including file and returning success
Date: Sat, 17 Dec 2022 20:39:35 +0100 [thread overview]
Message-ID: <20221217203935.2b62af25@homerow> (raw)
In-Reply-To: <20221217104111.8417@sachi>
On Sat, 17 Dec 2022 10:41:11 -0800
skyhorse--- via ntg-context <ntg-context@ntg.nl> wrote:
> The context wiki says:
> "When no file extension is specified the extension .tex is assumed."
It's not on the page for typefile:
https://wiki.contextgarden.net/Command/typefile
And that surely makes sense for TeX (input) files, but not \type'ed
files, which are usually not TeX files.
\startnitpicking
The message
verbatims > file 'bar' does not exist
is wrong, the file “bar” exists. Displaying
verbatims > file 'bar.txt' does not exist
\stopnitpicking
would be correct. But as I said, assuming \type'ed files are .tex
files does not make sense, IMO.
> By chance, do you have a file named "bar.tex" that would prevent this
> from being an error?
No. It just doesn't produce an error here (or non-success exit code
for that matter).
using LMTX: 2022.12.15 18:12
Marco
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-12-17 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 15:06 Marco Patzer via ntg-context
2022-12-17 15:25 ` Otared Kavian via ntg-context
2022-12-17 15:47 ` Marco Patzer via ntg-context
[not found] ` <484EE253-BF9E-4E91-94B8-0D627F334606@gmail.com>
2022-12-17 17:27 ` Marco via ntg-context
2022-12-21 12:17 ` Hans Hagen via ntg-context
2022-12-21 13:03 ` Marco Patzer via ntg-context
2023-02-21 13:12 ` Marco Patzer via ntg-context
2022-12-17 18:41 ` skyhorse--- via ntg-context
2022-12-17 19:39 ` Marco Patzer via ntg-context [this message]
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=20221217203935.2b62af25@homerow \
--to=ntg-context@ntg.nl \
--cc=lists@homerow.info \
/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).