ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jano Kula <jano.kula@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: files not readable
Date: Sat, 10 Apr 2021 18:03:03 +0200	[thread overview]
Message-ID: <CAPefzZ36HniCW2+7rervCCzxMKMaxmFxAPiwkepisRejz+6WaQ@mail.gmail.com> (raw)
In-Reply-To: <efabf76b-9ba7-eb1a-5b48-912c6badc9d5@xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]

On Sat, Apr 10, 2021 at 5:17 PM Hans Hagen <j.hagen@xs4all.nl> wrote:

>
> backend         > xmp > using file
> 'c:/data/develop/context/sources/lpdf-pdx.xml'


looks like lpdf-pdx.xml is used in the end:
backend   > xmp > using file
'C:/data/context/bin/beta-win64/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'
only  \enabletrackers[resolvers.details] adds the information "file not
readable", likely without any real effect.

I'm getting different results on windows and linux in more complex setup
and "file not readable" was the only difference in log files.
That's why I became interested in "file not readable" information, which
seems to be misleading.

In the end all files are are listed in
system > start used files
section and context doesn't complain it cannot open or read those files
(file not found).

The mystery of the log information remains unresolved.

Thank you,
Jano

[-- Attachment #1.2: Type: text/html, Size: 1663 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2021-04-10 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 13:10 Jano Kula
2021-04-10 13:29 ` Hans Hagen
2021-04-10 14:54   ` Jano Kula
2021-04-10 15:17     ` Hans Hagen
2021-04-10 16:03       ` Jano Kula [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=CAPefzZ36HniCW2+7rervCCzxMKMaxmFxAPiwkepisRejz+6WaQ@mail.gmail.com \
    --to=jano.kula@gmail.com \
    --cc=j.hagen@xs4all.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).