From: context@vivaldi.net
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt doesn't recognize source on network drive?
Date: Tue, 12 May 2020 11:26:33 +0200 [thread overview]
Message-ID: <8cfcf36d7f80ce249f4653f18f76ffa1@vivaldi.net> (raw)
In-Reply-To: <2d1460f7-1d93-394c-36ed-9802f2ea1b4a@xs4all.nl>
Hello Hans,
On 2020-05-12 10:58, Hans Hagen wrote:
> On 5/11/2020 5:26 PM, context@vivaldi.net wrote:
>> Hello,
>>
>> after I've updated ConTeXt to the latest version, a new problem
>> appeared - see the steps:
>>
>> (Note that "X:" is a network drive mapped as "\\192.168.112.xxx\px" -
>> if it was of importance.)
> i have no problem here running from a mapped drive (nothing changed in
> that areas either) and i would have noticed it as i have several
> network drives
here I'm running om Win7 64b.
I fixed the problem somehow:
- As normally I'm not running ConTeXt directly by "context.exe" but via
.bat file (some more actions to do), I added a code into .bat which
changes source file name from "x:\...\..." to "x:/...\...". (It's
performed by Lua's 'fname:gsub(":\\", ":/")' actually.) And it works
now.
(But my previously reported problem appeared on running 'context.exe',
i.e. without any auxiliary .bat.)
Lukas
> (i'm talking windows 10)
>
> Hans
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-05-12 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 15:26 context
2020-05-12 8:58 ` Hans Hagen
2020-05-12 9:26 ` 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=8cfcf36d7f80ce249f4653f18f76ffa1@vivaldi.net \
--to=context@vivaldi.net \
--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).