There is no pdf to read.
Uschi Hermann.
Sorry, dindn't write my name in the first Mail Today.
Von: Ursula Hermann
Gesendet: Montag, 04. September 2023 11:44
An: 'ntg-context@ntg.nl'
Am 04.09.23 um 12:25 schrieb Ursula Hermann:
After compiling the following example, which is from February 2021: I get: runtime error : input file './blackrule1.tex' is not found, quitting
Are you sure your file is called "blackrule1.tex" and exists in the same directory as you’re calling it? Hraban
Dear Henning,
Many thanks. That was the problem.
Uschi Hermann
-----Ursprüngliche Nachricht-----
Von: Henning Hraban Ramm
After compiling the following example, which is from February 2021: I get: runtime error : input file './blackrule1.tex' is not found, quitting
Are you sure your file is called "blackrule1.tex" and exists in the same directory as you’re calling it? Hraban ___________________________________________________________________________________ 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 ___________________________________________________________________________________
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
On 9/4/2023 7:03 PM, Pablo Rodriguez wrote:
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, here
context \\localhost\c$\data\develop\tmp\oeps.tex seems to be processed (with result in current path) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
On 9/4/23 19:14, Hans Hagen wrote:
here
context \\localhost\c$\data\develop\tmp\oeps.tex
seems to be processed (with result in current path)
Just in case it might be relevant, I was on W10. I would say that a similar command was right for me. But using Textadept 11.4 and invoking compilation from the editor triggered the error in my case. BTW, try "cd \\localhost\c$\data\develop\tmp" in the command prompt. It was impossible for me on W10. Pablo
participants (4)
-
Hans Hagen -
Henning Hraban Ramm -
Pablo Rodriguez -
Ursula Hermann