Re: "The input file could not be found"

Alexandre Borovik <[email protected]> Tue, 31 Jan 2017 18:16:29 +0000
Newsgroups gmane.comp.tex.miktex
Message-ID <[email protected]>
Thanks. I figure out the issue: it was in WinEdt 10 editor. Alexandre

On 31/01/2017 14:26, Ulrike Fischer wrote:
> Am Tue, 31 Jan 2017 09:01:51 +0000 schrieb Alexandre Borovik:
>
>> My MiKTeX (Windows 10, 64 bit) suddenly lost ability to see input file.
>> Reinstallation did not help. Could you please help?
>>
>> Alexandre
>>
>> <<<ERROR MESSAGE:
>>
>> Command Line:   texify.exe --pdf
>> --tex-option=--interaction=errorstopmode --tex-option=--synctex=-1
>> "C:\Users\AB\Documents\Current\10212
>> 2016-17\10212_Slides_2016-17_Weeks_1-4.tex"
>> Startup Folder: C:\Users\AB\Documents\Current\10212 2016-17
>>
>>
>> Sorry, but texify did not succeed for the following reason:
>>
>>    The input file could not be found.
>
> I can't reproduce the problem on windows 10 + miktex 32bit. But
>
> - don't use spaces in folder/file names
> - don't call texify (and other applications) with absolute files
> names.
> - don't use texify at all - imho it is a pain. It fails constantly
> and its error messages are bad. If you want a tool for an automatic
> compilation use latexmk or arara.
>

-- 
Alexandre Borovik
Web:  www.borovik.net
Blog: www.borovik.net/selecta

The views expressed do not necessarily represent
the position of my employer or any other person,
organisation, or institution.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Q: How can I leave the mailing list?
A: See http://docs.miktex.org/faq/support.html#leavingml