From: Marco Patzer via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Marco Patzer <lists@homerow.info>
Subject: Re: \typefile not including file and returning success
Date: Tue, 21 Feb 2023 14:12:30 +0100 [thread overview]
Message-ID: <20230221141230.00a99752@homerow> (raw)
In-Reply-To: <796dff7e-ef1f-7200-90c3-98e98efb8447@freedom.nl>
On Wed, 21 Dec 2022 13:17:15 +0100
Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:
> The next upload will have:
>
> \adddefaultsuffix[foo,{},crap]
> \adddefaultsuffix[{}]
>
> \typefile{./crapcrap}
> \typefile{crapcrap}
>
> which someone has to document on the wiki
Apologies for taking so long. But I just now tested your fix and
wanted to remove the absolute paths from my document and found that
either your fix is not working or I'm doing something wrong
(probably the latter). Example:
# create file “bar”
echo Bar > bar
%% \adddefaultsuffix[foo,{},crap,bar]
\adddefaultsuffix[{}]
\starttext
Foo
\typefile{bar}
\stoptext
This does *not* include the file “bar”. As far as I understand:
%% searches for files with no extention
\adddefaultsuffix[{}]
%% searches for files with extension aa, bb, foobar,
%% e.g. file.aa, blurp.bb or example.foobar
\adddefaultsuffix[aa, bb, foobar]
But that's not how it behaves. Can you elaborate?
Marco
LMTX 2023.02.14 17:44
PS: When I get it to work, I'll document it on the wiki.
___________________________________________________________________________________
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:[~2023-02-21 13:12 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 [this message]
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=20230221141230.00a99752@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).