From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: After compiling
Date: Mon, 4 Sep 2023 19:03:24 +0200 [thread overview]
Message-ID: <6a4f4117-103a-237c-3d86-4270374cdcd8@gmx.es> (raw)
In-Reply-To: <f6991542c6644da894c1792bcda45d30@univie.ac.at>
On 9/4/23 12:25, Ursula Hermann wrote:
> There is no pdf to read.
> Uschi Hermann.
> Sorry, dindn’t write my name in the first Mail Today.
Hi Uschi,
sorry for explaining what might be obvious to you now, but I think
knowing the cause might be worth it
> After compiling the following example, which is from February 2021:
Unfortunately, there was no compilation (source not found).
> "\\ub.univie.ac.at\U_Dom\Users G-L\Hermann\Documents\Texlive"
> CMD.EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis
> gestartet.
> UNC-Pfade werden nicht untersttzt.
> Stattdessen wird das Windows-Verzeichnis als aktuelles Verzeichnis gesetzt.
This is the real problem: UNC paths and the command prompt (CMD.EXE).
UNC paths are a Windows way to access remote units (let’s say it so).
They are similar to: "\\remote-server\directory\subdirectory\file.tex".
CMD is required by ConTeXt to run, but CMD doesn’t understand UNC paths,
so it switches the directory to the %SYSTEMROOT% (usually, C:\Windows).
This directory shouldn’t be writable (without admin rights).
So the file cannot be found, since the directory is not the one that
contains the source.
Using Explorer, it is possible to give a path such as
"\\localhost\c$\Users\USERNAME\whatever\file.txt" and open it with your
favourite editor, but it will be impossible to compile.
UNC paths in common used are mapped as local units, such as (explained
in https://ss64.com/nt/net-use.html#e):
net use X: "\\remote-server\directory\"
That way compiling x:\subdirectory\file.tex would be no problem.
> runtime error : input file './blackrule1.tex' is not found, quitting
Hraban was right: there might be no %SYSTEMROOT%\blackrule1.tex.
Just in case it might help to understand was what wrong,
Pablo
___________________________________________________________________________________
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-09-04 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 10:25 [NTG-context] " Ursula Hermann
2023-09-04 10:42 ` [NTG-context] " Henning Hraban Ramm
2023-09-04 11:02 ` Ursula Hermann
2023-09-04 17:03 ` Pablo Rodriguez [this message]
2023-09-04 17:14 ` Hans Hagen
2023-09-04 17:26 ` Pablo Rodriguez
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=6a4f4117-103a-237c-3d86-4270374cdcd8@gmx.es \
--to=oinos@gmx.es \
--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).