From: Marco Patzer via ntg-context <ntg-context@ntg.nl>
To: Otared Kavian via ntg-context <ntg-context@ntg.nl>
Cc: Marco Patzer <lists@homerow.info>, Otared Kavian <otared@gmail.com>
Subject: Re: \typefile not including file and returning success
Date: Sat, 17 Dec 2022 16:47:12 +0100 [thread overview]
Message-ID: <20221217164712.094bbc5e@homerow> (raw)
In-Reply-To: <C52B98CA-A599-4CD0-8156-D0D515209B64@gmail.com>
On Sat, 17 Dec 2022 16:25:01 +0100
Otared Kavian via ntg-context <ntg-context@ntg.nl> wrote:
> If I create a file named « bar.txt » then
>
> \starttext
> Nothing to say\dots
>
> \typefile{bar.txt}
>
> \stoptext
>
> gives the correct result.
I can confirm that.
> However ConTeXt seems to dislike \typefile{bar} when the filename
> has no suffix.
Is there a way around it? Traditionally there are plenty of files
without suffix (e.g. README, Makefile, configure, etc.)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-17 15:47 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 [this message]
[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
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=20221217164712.094bbc5e@homerow \
--to=ntg-context@ntg.nl \
--cc=lists@homerow.info \
--cc=otared@gmail.com \
/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).