Re: AUCTex in WSL cannot find TeX Live in Win
Hi Pete, > petepetit...@my.mail.de writes: >> What happens when you insert >> (call-process TeX-shell nil t nil >> TeX-shell-command-option "tex.exe --version") >> in *scratch* buffer in wsl emacs and type C-x C-e just after the closing >> ")"? > After I load auctex (by loading my test2.tex in emacs) and type the > above lines in *scratch*, this is how the buffer looks like: > (call-process TeX-shell nil t nil > TeX-shell-command-option "tex.exe --version")TeX 3.141592653 (TeX Live 2022) > kpathsea version 6.3.4 > Copyright 2022 D.E. Knuth. > There is NO warranty. Redistribution of this software is > covered by the terms of both the TeX copyright and > the Lesser GNU General Public License. > For more information about these matters, see the file > named COPYING and the TeX source. > Primary author of TeX: D.E. Knuth. > Does not look ignorant of my Windows Tex Live installation, in > principle. Thanks, now it's clear that synchronous process invocation through works well for TeX Live binary. > But should there still be no easy remedy in sight, I suggest I don't > steal any more of your precious time and just move Tex Live inside the > walls of wsl. I see. If you want to tackle this issue again some day, I recommend to ask on help-gnu-em...@gnu.org . The points are, on wsl, 1. In emacs, synchronous invocation of windows binary through bash works well. 2. In emacs, asynchronous invocation of linux binary through bash works well. 3. On bash console (not in emacs), asynchronous invocation of windows binary through (another) bash works well. 4. However, asynchronous invocation of windows binary through bash in emacs doesn't work. Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Ikumi, > What happens when you insert > (call-process TeX-shell nil t nil > TeX-shell-command-option "tex.exe --version") > in *scratch* buffer in wsl emacs and type C-x C-e just after the closing > ")"? After I load auctex (by loading my test2.tex in emacs) and type the above lines in *scratch*, this is how the buffer looks like: (call-process TeX-shell nil t nil TeX-shell-command-option "tex.exe --version")TeX 3.141592653 (TeX Live 2022) kpathsea version 6.3.4 Copyright 2022 D.E. Knuth. There is NO warranty. Redistribution of this software is covered by the terms of both the TeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the TeX source. Primary author of TeX: D.E. Knuth. Does not look ignorant of my Windows Tex Live installation, in principle. But should there still be no easy remedy in sight, I suggest I don't steal any more of your precious time and just move Tex Live inside the walls of wsl. Thanks a lot and wish you a pleasant weekend! Kind regards, Pete - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Pete, > petepetit...@my.mail.de writes: > Oh no, not me again. Just in case anybody might be interested and so > that really nothing remains unattempted, I did a 'ground-zero' fresh > installation of wsl + Ubuntu 20.04 LTS. > I haven't reproduced all of Ikumi's steps, but the result seems > exactly the same: > 1. From within wsl-emacs + auctex no windows Tex Live-installation can > be found, replacing commands by their corresponing .exe to no > substantial avail, etc. p.p. > 2. Flawless compilation and production of a pdf from tex-file, when > pdflatex.exe is manually executed outside wsl-Emacs in (now-) Ubuntu > console: pdflatex.exe test2.tex > So rather than anything being wrong wsl, probably "then emacs running > under wsl has something wrong about starting asynchronous process of > windows binary." (cit. Ikumi) Let me summarise the situation. (a) When Pete added ".exe" to `TeX-command' and `LaTeX-command', AUCTeX began to pass the existence check of TeX binary in the function `TeX-command'[1]. Hence (call-process TeX-shell nil nil nil TeX-shell-command-option TeX-command)) began to run successfully. This means that synchronous invocation of tex.exe through bash succeeded. (b) However, AUCTeX still failed to typeset by C-c C-c. Together with the result of a separate experiment[2], we see (start-process name buffer TeX-shell TeX-shell-command-option command) in the function `TeX-run-command' doesn't run the command actually. This means that asynchronous invocation of pdflatex.exe through bash didn't succeed. [1] https://lists.gnu.org/r/auctex/2022-08/msg00014.html [2] https://lists.gnu.org/r/auctex/2022-08/msg00018.html It's quite puzzling why this difference between synchronous and asynchronous invocation occurs. Hmm, maybe my interpretation of (a) was wrong? Since `TeX-command' checks only whether the exit code is 127 or not, it doesn't complain when the command didn't actually run. What happens when you insert (call-process TeX-shell nil t nil TeX-shell-command-option "tex.exe --version") in *scratch* buffer in wsl emacs and type C-x C-e just after the closing ")"? Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
> Maybe you should try another instance
> of wsl installation, say Ubuntu, to see whether AUCTeX runs as expected
> or not. If it fails as well, then emacs running under wsl has something
> wrong about starting asynchronous process of windows binary. On the
> contrary, if it runs normally, then your current installation of Debian
> wsl is somehow corrupted.
Oh no, not me again. Just in case anybody might be interested and so that
really nothing remains unattempted, I did a 'ground-zero' fresh installation of
wsl + Ubuntu 20.04 LTS.
I haven't reproduced all of Ikumi's steps, but the result seems exactly the
same:
1. From within wsl-emacs + auctex no windows Tex Live-installation can be
found, replacing commands by their corresponing .exe to no substantial avail,
etc. p.p.
2. Flawless compilation and production of a pdf from tex-file, when
pdflatex.exe is manually executed outside wsl-Emacs in (now-) Ubuntu console:
pdflatex.exe test2.tex
So rather than anything being wrong wsl, probably "then emacs running under wsl
has something
wrong about starting asynchronous process of windows binary." (cit. Ikumi)
Btw, One user besides me with the same setup seems to have encountered the very
same issue:
https://tex.stackexchange.com/questions/519687/is-there-any-way-to-run-windows-texlive-on-wsl
One commentator gives a hint that he has managed to get it working with
pdflatex.exe, as I understand it he does not say whether in wsl-console or via
emacs.
Kind regards!
Pete
Edit: After just re-reading the user's question on tex-stackexchange, I correct
myself: he did not say he encountered an issue, but was wise enough to ask
beforehand. I also assume the commentator got it to work via the console, as in
the thread there is no mention of emacs.
I don't understanding every line, but it seems wsl has no qualms accessing Win/
Tex Live
pdflatex.exe test2.tex--->
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022) (preloaded
format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./test2.tex
LaTeX2e patch level 1
L3 programming layer
(c:/texlive/2022/texmf-dist/tex/latex/base/article.cls
Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
(c:/texlive/2022/texmf-dist/tex/latex/base/size10.clo))
(c:/texlive/2022/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def)
No file test2.aux.
[1{c:/texlive/2022/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] (./test2.aux)
)
Output written on test2.pdf (1 page, 12756 bytes).
Transcript written on test2.log.
-
FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT
-
FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> Maybe you should try another instance > of wsl installation, say Ubuntu, to see whether AUCTeX runs as expected > or not. If it fails as well, then emacs running under wsl has something > wrong about starting asynchronous process of windows binary. On the > contrary, if it runs normally, then your current installation of Debian > wsl is somehow corrupted. Oh no, not me again. Just in case anybody might be interested and so that really nothing remains unattempted, I did a 'ground-zero' fresh installation of wsl + Ubuntu 20.04 LTS. I haven't reproduced all of Ikumi's steps, but the result seems exactly the same: 1. From within wsl-emacs + auctex no windows Tex Live-installation can be found, replacing commands by their corresponing .exe to no substantial avail, etc. p.p. 2. Flawless compilation and production of a pdf from tex-file, when pdflatex.exe is manually executed outside wsl-Emacs in (now-) Ubuntu console: pdflatex.exe test2.tex So rather than anything being wrong wsl, probably "then emacs running under wsl has something wrong about starting asynchronous process of windows binary." (cit. Ikumi) Btw, One user besides me with the same setup seems to have encountered the very same issue: https://tex.stackexchange.com/questions/519687/is-there-any-way-to-run-windows-texlive-on-wsl One commentator gives a hint that he has managed to get it working with pdflatex.exe, as I understand it he does not say whether in wsl-console or via emacs. Kind regards! Pete - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> It doesn't seem "always". According to one of your replies[1], > cmd.exe /c cd > warned that "CMD.EXE wurde mit..." and started in fallback directory > "C:\Windows". I suppose those results indicate that cmd.exe encountered > something unexpected and couldn't run normally. edit: "almost always" - > which in the binary realm of 1/0 can never be satisfying enough, you are > right. > The behavior seems unpredictable to me. Just to confirm the > result one last time and exclude the human unreliability-factor, I tried > again:cmd.exe /c cdin debian console results in the above stated > warning "CMD.EXe wurde dem oben angegebenen [...]. It might be even the > right time to just completely switch OS from Win to Linux. Thanks and > regards to all, Pete - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> petepetit...@my.mail.de writes: >> Does this command, taken from [1], list contents of your Windows files >> C:\ directory? >> cmd.exe /C dir >> (Run the above command in the wsl bash connsole.) > Yes, this run-down lists my Windows C:\ directory. Everything run in > wsl-console seems to always exceute the desired result. It doesn't seem "always". According to one of your replies[1], cmd.exe /c cd warned that "CMD.EXE wurde mit..." and started in fallback directory "C:\Windows". I suppose those results indicate that cmd.exe encountered something unexpected and couldn't run normally. [1] https://lists.gnu.org/r/auctex/2022-08/msg00033.html The behavior seems unpredictable to me. Sorry, I'm giving up. > This or for now, until perhaps this issue will be resolved with future > distributions, I'll just have to install Texlive within Debian. > Running pdflatex.exe from the console and having no preview just does > not seem to be a very practical workflow. Thank you so very much for > your truly dedicated help, Ikumi! I still feel I have learned > something from your also didactically excellent instructions. Computer > science is obviously not my business, still you never lost patience. > Domo arigato und Dankeschön! In case any significant change in the > status quo should come about in the future, I will make notice. So it > can maybe be use who encounter the same issue. Kind regards, Pete Thank you for warmful comments. I hope the issue would be resoved some day... Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Arash, Thank you very much for the suggestion. That looks to me like an expert-workaround that would exceed my (rudimentally existent at best, as should have become clear) capabilities even further, though Perhaps, there are just not enough people that use my setup, so that going through the trouble would probably be in no justifiable relation.Kind regards, Pete I didn't follow this thread closely, so sorry if my next suggestion is totally off. Maybe it works if one writes some small wrapper bash scripts in WSL which then runs the Windows executables. I run tlmgr.bat in bash (coming with Msys2) on Windows like this: -> which tlmgr /usr/local/bin/tlmgr -> cat `which tlmgr` #!/bin/sh # This is a small wrapper around tlmgr.bat in order to use it under # bash from Msys2. Note the double // for escaping / cmd.exe //c tlmgr.bat "$@"; exit $? Note that // is a Msys2-thing. cmd.exe and tlmgr.bat are in my $PATH which looks like this in a MinGW64 bash-console (linebreaks added for better legibility): -> echo $PATH /mingw64/bin: /usr/local/bin: /usr/bin: /bin: /c/Windows/System32: /c/Windows: /z/pathto/texlive/2022/bin/win32: ... So I would write a wrapper to pdflatex, put it under WSL somewhere in $PATH, put an entry for WSLENV[1] in it if necessary, and then start Emacs and see if it works and AUCTeX finds the binary/script. Best, Arash Footnotes: [1] https://devblogs.microsoft.com/commandline/share-environment-vars-between-wsl-and-windows/ - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> Does this command, taken from [1], list contents of your Windows files > C:\ directory? > cmd.exe /C dir > (Run the above command in the wsl bash connsole.) Yes, this run-down lists > my Windows C:\ directory. Everything run in wsl-console seems to always > exceute the desired result. > Maybe you should try another instance > of wsl installation, say Ubuntu, to see whether AUCTeX runs as expected > or not. If it fails as well, then emacs running under wsl has something > wrong about starting asynchronous process of windows binary. On the > contrary, if it runs normally, then your current installation of Debian > wsl is somehow corrupted. This or for now, until perhaps this issue will > be resolved with future distributions, I'll just have to install Texlive > within Debian. Running pdflatex.exe from the console and having no preview > just does not seem to be a very practical workflow. Thank you so very much > for your truly dedicated help, Ikumi! I still feel I have learned something > from your also didactically excellent instructions. Computer science is > obviously not my business, still you never lost patience. Domo arigato und > Dankeschön!In case any significant change in the status quo should come > about in the future, I will make notice. So it can maybe be use who encounter > the same issue.Kind regards, Pete - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Ikumi Keita writes: >> petepetit...@my.mail.de writes: >> >> One intuition (though it is mainly just that) I may be not wrong >> about, remains: Wsl is quite alright, but there is something that >> emacs/ aucteX, vulgo, don't get. Back to square 1, I guess... > > I'm almost running out of ideas. I didn't follow this thread closely, so sorry if my next suggestion is totally off. Maybe it works if one writes some small wrapper bash scripts in WSL which then runs the Windows executables. I run tlmgr.bat in bash (coming with Msys2) on Windows like this: -> which tlmgr /usr/local/bin/tlmgr -> cat `which tlmgr` #!/bin/sh # This is a small wrapper around tlmgr.bat in order to use it under # bash from Msys2. Note the double // for escaping / cmd.exe //c tlmgr.bat "$@"; exit $? Note that // is a Msys2-thing. cmd.exe and tlmgr.bat are in my $PATH which looks like this in a MinGW64 bash-console (linebreaks added for better legibility): -> echo $PATH /mingw64/bin: /usr/local/bin: /usr/bin: /bin: /c/Windows/System32: /c/Windows: /z/pathto/texlive/2022/bin/win32: ... So I would write a wrapper to pdflatex, put it under WSL somewhere in $PATH, put an entry for WSLENV[1] in it if necessary, and then start Emacs and see if it works and AUCTeX finds the binary/script. Best, Arash Footnotes: [1] https://devblogs.microsoft.com/commandline/share-environment-vars-between-wsl-and-windows/
Re: AUCTex in WSL cannot find TeX Live in Win
> petepetit...@my.mail.de writes: > Right! Referring to the wsl-doc which first seemed confusing, I was > able to identify one major culprit: myself. Wsl, of course, has to be > running in the background for "\\wsl$" to show the desired result. > (I could have realized myself, as when clicking on the popped-up > "network" folder windows complains there is no active network) So > when asked correctly, the folder Debian (shown in Explorer as > Netzwerk > wsl$ > Debian) pops up correctly, too. That was mistake > No.1 OK. > Mistake No.2: I indeed forgot not include the period. When I do, > folder citizen13 does pop up in windows. Full path displayed in > explorer: Netzwerk > wsl$ > Debian > home > citizen13 Hmm, then it's quite puzzling why cmd.exe refused the path "\\wsl$..." previously... Does this command, taken from [1], list contents of your Windows files C:\ directory? cmd.exe /C dir (Run the above command in the wsl bash connsole.) [1] https://docs.microsoft.com/en-us/windows/wsl/filesystems#run-windows-tools-from-linux > Certainly, you were bound to come that conclusion, because in spite of > giving such precise instructions that even beginners should be able to > follow, the problem was sitting in front of my machine. Sorry for the > confusion! One intuition (though it is mainly just that) I may be not > wrong about, remains: Wsl is quite alright, but there is something > that emacs/ aucteX, vulgo, don't get. Back to square 1, I guess... I'm almost running out of ideas. Maybe you should try another instance of wsl installation, say Ubuntu, to see whether AUCTeX runs as expected or not. If it fails as well, then emacs running under wsl has something wrong about starting asynchronous process of windows binary. On the contrary, if it runs normally, then your current installation of Debian wsl is somehow corrupted. Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
> That shouldn't be empty. According to the doc[1], it should list Linux > distributions and their root file systems as the image shown there. Right! Referring to the wsl-doc which first seemed confusing, I was able to identify one major culprit: myself. Wsl, of course, has to be running in the background for "\\_wsl$" _to show the desired result. (I could have realized myself, as when clicking on the popped-up "network" folder windows complains there is no active network) So when asked correctly, the folder Debian (shown in Explorer as Netzwerk > wsl$ > Debian) pops up correctly, too. That was mistake No.1 _> _2. What happens when you issue > explorer.exe . > in wsl bash console? > (a) Does that display the linux files in the directory where you issued > the command? Or is that empty? > (b) What is shown in the address bar of that explorer? > (Make sure to include the period "." at the last of the command; i.e., > not > explorer.exe > but > explorer.exe . Mistake No.2: I indeed forgot not include the period. > When I do, folder citizen13 does pop up in windows. Full path displayed in > explorer: Netzwerk > wsl$ > Debian > home > citizen13 > Anyway, it's certain that your wsl isn't working as expected according > to the result of 1. Certainly, you were bound to come that conclusion, > because in spite of giving such precise instructions that even beginners > should be able to follow, the problem was sitting in front of my machine. > Sorry for the confusion! One intuition (though it is mainly just that) I > may be not wrong about, remains: Wsl is quite alright, but there is something > that emacs/ aucteX, vulgo, don't get. Back to square 1, I guess... Kind > regards and Thank you very much, Pete - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> Ikumi Keita writes: > Anyway, it's certain that your wsl isn't working as expected according > to the result of 1. I recommend to follow the instruction at [2] again. > And I think the current issue has nothing to do with AUCTeX itself. > [2] https://docs.microsoft.com/en-us/windows/wsl/filesystems Sorry, the URL should have been https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#cannot-access-wsl-files-from-windows Bye, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
> petepetit...@my.mail.de writes: >> 1. What happens when you enter >> \\wsl$ >> in the address bar of windows explorer? (not in wsl) > address bar shows: Netzwerk ( = network) > wsl$ > while it's saying: Dieser Ordner ist leer (= This directory is empty) That shouldn't be empty. According to the doc[1], it should list Linux distributions and their root file systems as the image shown there. [1] https://docs.microsoft.com/en-us/windows/wsl/filesystems#view-your-current-directory-in-windows-file-explorer >> 2. What happens when you issue >> explorer.exe . >> in wsl bash console? > Success. This actually opens the windows-explorer. (a) Does that display the linux files in the directory where you issued the command? Or is that empty? (b) What is shown in the address bar of that explorer? (Make sure to include the period "." at the last of the command; i.e., not explorer.exe but explorer.exe . ^^ ) Anyway, it's certain that your wsl isn't working as expected according to the result of 1. I recommend to follow the instruction at [2] again. And I think the current issue has nothing to do with AUCTeX itself. [2] https://docs.microsoft.com/en-us/windows/wsl/filesystems Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
> 1. What happens when you enter > \\wsl$ > in the address bar of windows explorer? (not in wsl) address bar shows: > Netzwerk ( = network) > wsl$ while it's saying: Dieser Ordner ist leer (= > This directory is empty)Again, I have to leave it to your expertise for > how sane that has to be taken. > 2. What happens when you issue > explorer.exe . > in wsl bash console? Success. This actually opens the windows-explorer. > If 1. or 2., or both, doesn't return sane result, I suspect that your > installation of wsl is somewhat broken. As every command via the wsl bash > console seems to execute all *.exes including pdflatex.exe correctly, could > this not rather be a hint that wsl itself is working and interacting with > windows perfectly fine? But that just something in the > communication-interface between wsl-emacs/ auctex and wsl or wls-emacs/ > auxteX and windows seems wrong or perhaps lacking? Kind regards, Pete - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> petepetit...@my.mail.de writes: >> 1. On windows side (not in wsl), does the directory >> "\\wsl$\Debian\home\citizen13" exist actually? > Although I feel inclined to answer "no". It could not be be a valid > abbreviation of my debian-wsl home directory This must be the culprit. It seems that the wsl document[1] indicated by Arash (thanks Arash!) instructs to use the directory of the form \\wsl$\\home\ as the wsl home directory from windows side: "Use the Linux file system root directory: \\wsl$\Ubuntu\home\\Project" "..., but your performance speed will improve if you store them directly on the \\wsl$ drive." "To view all of your available Linux distributions and their root file systems in Windows File explorer, in the address bar enter: \\wsl$" 1. What happens when you enter \\wsl$ in the address bar of windows explorer? (not in wsl) 2. What happens when you issue explorer.exe . in wsl bash console? If 1. or 2., or both, doesn't return sane result, I suspect that your installation of wsl is somewhat broken. Consult the troubleshoot section: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#cannot-access-wsl-files-from-windows [1] https://docs.microsoft.com/en-us/windows/wsl/filesystems Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Ikumi, > I assume that it didn't open a command prompt actually.Correct, no > command prompt opened. > 1. On windows side (not in wsl), does the directory > "\\wsl$\Debian\home\citizen13" exist actually? Although I feel inclined to > answer "no". It could not be be a valid abbreviation of my debian-wsl home > directory which is installed in and can be accessed from the windows side > via?: > C:\Users\[...]\AppData\Local\Packages\TheDebianProject.DebianGNULinux_[]\LocalState\rootfs\home\citizen13 > > 2. What does > cmd.exe /c cd > report on wsl bash prompt (not in emacs)? "\\wsl$\Debian\home\citizen13" CMD.EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis gestartet. UNC-Pfade werden nicht unterstützt. Stattdessen wird das Windows-Verzeichnis als aktuelles Verzeichnis gesetzt. C:\Windows And no command prompt opens. Kind regards, Pete - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> Ikumi Keita writes: > I assume that it didn't open a command prompt actually. Sorry, this part wasn't quite correct. The prompt "C:\Windows>" was there, so cmd.exe did start as console-application (?) and didn't open its own window. Maybe pdflatex.exe ran in a similar way in the directory "C:\Windows>" and could not find helloworld.tex there? Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
> Ikumi Keita writes: > I assume that it didn't open a command prompt actually. Sorry, this part wasn't quite correct. The prompt "C:\Windows>" was there, so cmd.exe did start as console-application (?) and didn't open its own window. Maybe pdflatex.exe ran in a similar way in the directory "C:\Windows>" and could not find helloworld.tex there? Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
> petepetit...@my.mail.de writes: > Weird. After - though not expecting anything to change - trying your > suggestion a second time: >> How about >> (let ((process-connection-type nil)) >> (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option >> "cmd.exe")) >> then? Does it open a windows command prompt? > This time the following popped up, not in the minibuffer, but in the > same buffer "scratch", just after the last ")" in your command: > "\\wsl$\Debian\home\citizen13" > CMD.EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis > gestartet. > UNC-Pfade werden nicht unterstützt. > Stattdessen wird das Windows-Verzeichnis als aktuelles Verzeichnis gesetzt. > Microsoft Windows [Version 10.0.19044.1889] > (c) Microsoft Corporation. Alle Rechte vorbehalten. C:\Windows> > Quick & dirty translation: CMD.EXE was started with the above stated > path as present directory. UNC-paths are not supported. Instead the > windows-directory is being set as present directory. Microsoft [...] > etc. (c) [...] All rights reserved. C:\Windows > Makes a non-technical person wonder: May this be considered a success > or the contrary? I assume that it didn't open a command prompt actually. Then the request was transmitted to windows side, and windows tried to start cmd.exe. However, the current directory "\\wsl$\Debian\home\citizen13" was considered invalid. Hmm... I wonder why pdflatex.exe ran successfully on wsl bash prompt, then. 1. On windows side (not in wsl), does the directory "\\wsl$\Debian\home\citizen13" exist actually? 2. What does cmd.exe /c cd report on wsl bash prompt (not in emacs)? Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Weird. After - though not expecting anything to change - trying your suggestion a second time: > How about > (let ((process-connection-type nil)) > (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option > "cmd.exe")) > then? Does it open a windows command prompt? This time the following > popped up, not in the minibuffer, but in the same buffer "scratch", just > after the last ")" in your command: "\\wsl$\Debian\home\citizen13" CMD.EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis gestartet. UNC-Pfade werden nicht unterstützt. Stattdessen wird das Windows-Verzeichnis als aktuelles Verzeichnis gesetzt. Microsoft Windows [Version 10.0.19044.1889] (c) Microsoft Corporation. Alle Rechte vorbehalten. C:\Windows> Quick & dirty translation: CMD.EXE was started with the above stated path as present directory. UNC-paths are not supported. Instead the windows-directory is being set as present directory. Microsoft [...] etc. (c) [...] All rights reserved. C:\Windows Makes a non-technical person wonder: May this be considered a success or the contrary? - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Weird. After - though not expecting anything to change - trying your suggestion a second time: > How about > (let ((process-connection-type nil)) > (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option > "cmd.exe")) > then? Does it open a windows command prompt? This time the following > popped up, not in the minibuffer, but in the same buffer "scratch", just > after the last ")" in your command: "\\wsl$\Debian\home\citizen13" CMD.EXE wurde mit dem oben angegebenen Pfad als aktuellem Verzeichnis gestartet. UNC-Pfade werden nicht unterstützt. Stattdessen wird das Windows-Verzeichnis als aktuelles Verzeichnis gesetzt. Microsoft Windows [Version 10.0.19044.1889] (c) Microsoft Corporation. Alle Rechte vorbehalten. C:\Windows> Quick & dirty translation: CMD.EXE was started with the above stated path as present directory. UNC-paths are not supported. Instead the windows-directory is being set as present directory. Microsoft [...] etc. (c) [...] All rights reserved. C:\Windows Makes a non-technical person wonder: May this be considered a success or the contrary? - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Greetings Ikumi,
> Then, wsl emacs cannot start asynchronous process of windows binary via
> "bash -c", while bash itself can. I wonder what the difference is. Looks
> tricky. Do you think there is a reasonable chance at all, this could be
> easily resolved? I'm beginning to fear, my 'patient' may turn out to be a
> hopeless case and it has taken too much of your precious time, already.
> How about
> (let ((process-connection-type nil))
> (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option
> "cmd.exe"))
> then? Does it open a windows command prompt? Not either, i.e. again ("#")
> ;(
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
-
FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> petepetit...@my.mail.de writes:
>> 1. Start wsl emacs session and load AUCTeX (i.e., open some (La)TeX
>> document.)
>> 2. Insert
>> (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option
>> "cmd.exe")
>> at the last of *scratch* buffer and type C-x C-e just after the
>> closing ")". Does it open a windows command prompt successfully? If
>> not, what does emacs report?
> Again, that same process-dummy msg that gets mutilated by mail.de Hope
> it is displayed in full this way: ("#")
Then, wsl emacs cannot start asynchronous process of windows binary via
"bash -c", while bash itself can. I wonder what the difference is.
How about
(let ((process-connection-type nil))
(start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option
"cmd.exe"))
then? Does it open a windows command prompt?
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Ikumi,
> Ah, I see. Your MUA seems broken at generating plain text alternative
> part. I guess it dismisses everything between "", whereas it
> retains "" in the html alternative. Probably "FreeMail
> powered by mail.de" is responsible for that. (I prefer plain text over
> html format, so I configured my MUA to display plain text alternative
> rather than html alternative.)
Thank you for the hint, good to hear at least it was not my own mistake. I will
yet have to find out how to switch to plain text in mail.de.
> I think that you have cmd.exe in your PATH and expect that
> cmd.exe
Are you saying that I should have cmd.exe in my windows PATH
environment-variables? Then I suppose I do, because I have
%SystemRoot&\system32 which should contain cmd.exe.
> on wsl console opens windows command prompt. If it does, close it by
> entering "exit" at the prompt and try the following:
> 1. Start wsl emacs session and load AUCTeX (i.e., open some (La)TeX
> document.)
> 2. Insert
> (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option
> "cmd.exe")
> at the last of *scratch* buffer and type C-x C-e just after the
> closing ")". Does it open a windows command prompt successfully? If
> not, what does emacs report?
Again, that same process-dummy msg that gets mutilated by mail.de Hope it is
displayed in full this way: ("#")
It seems to be a tricky case. Thanks once again for your patience.
-
FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Pete, > petepetit...@my.mail.de writes: >> Do you mean that only a single "#" appeared in the echo area? Not >> "#"? And didn't emacs signal an error? > Oops, pardon me, rest of the line in my posting got swallowed up; "#" > is what I get, you are correct. Ah, I see. Your MUA seems broken at generating plain text alternative part. I guess it dismisses everything between "<" and ">", whereas it retains "" in the html alternative. Probably "FreeMail powered by mail.de" is responsible for that. (I prefer plain text over html format, so I configured my MUA to display plain text alternative rather than html alternative.) Then emacs thinks that asynchronous TeX process has started successfully. The problems is that the process actually doesn't run. >> Hmm... What happens when you issue the following command on the wsl bash >> console? (not in emacs) >> bash -c "tex.exe --version" & > This: [1] 21 TeX 3.141592653 (TeX Live 2022) [...] OK. Then windows binary runs without problem when it is called indirectly through "bash -c" under asynchronous invocation. I think that you have cmd.exe in your PATH and expect that cmd.exe on wsl console opens windows command prompt. If it does, close it by entering "exit" at the prompt and try the following: 1. Start wsl emacs session and load AUCTeX (i.e., open some (La)TeX document.) 2. Insert (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option "cmd.exe") at the last of *scratch* buffer and type C-x C-e just after the closing ")". Does it open a windows command prompt successfully? If not, what does emacs report? Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Please forget everything regarding my "ingenious" idea regarding cygwin: cygwin has it's own texlive-environment, so all comparisons make zero sense. Apologies for adding to the confusion! Am 25-Aug-2022 19:26:22 +0200 schrieb petepetit...@my.mail.de: > I just got another idea. Before switching wsl, I had emacs/ aucteX succesfully running 'out-of-the box' under cygwin. > Were this not comparable conditions, .i.e. a subsystem in which emacs/ aucteX had to fetch the pdflatex.exe in Tex Live > in Windows. So, maybe it could be helpful to reinstall that again and compare entries in corresponding .init- or .emacs > files? I gave it a try. Just added another question mark, though: Strangely, emacs/aucteX in cygwin seems to be executing just 'latex' and 'tex' without .exe to succesfully access Tex Live in Windows. That is what is written in the aucteX-menu, at least. What I also noticed: Contrary to wsl, in cygwin there no teX-related lines at all in .emacs. - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Forget everything regarding my "ingenious" idea regarding cygwin: cygwin has it's own texlive-environment, so all comparisons make zero sense. Apologies for adding to the confusion! Am 25-Aug-2022 19:26:22 +0200 schrieb petepetit...@my.mail.de: > I just got another idea. Before switching wsl, I had emacs/ aucteX succesfully running 'out-of-the box' under cygwin. > Were this not comparable conditions, .i.e. a subsystem in which emacs/ aucteX had to fetch the pdflatex.exe in Tex Live > in Windows. So, maybe it could be helpful to reinstall that again and compare entries in corresponding .init- or .emacs > files? I gave it a try. Just added another question mark, though: Strangely, emacs/aucteX in cygwin seems to be executing just 'latex' and 'tex' without .exe to succesfully access Tex Live in Windows. That is what is written in the aucteX-menu, at least. What I also noticed: Contrary to wsl, in cygwin there no teX-related lines at all in .emacs. - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
> I just got another idea. Before switching wsl, I had emacs/ aucteX > succesfully running 'out-of-the box' under cygwin. > Were this not comparable > conditions, .i.e. a subsystem in which emacs/ aucteX had to fetch the > pdflatex.exe in Tex Live > in Windows. So, maybe it could be helpful to > reinstall that again and compare entries in corresponding .init- or .emacs > > files? I gave it a try. Just added another question mark, though: > Strangely, emacs/aucteX in cygwin seems to be executing just 'latex' and > 'tex' without .exe to succesfully access Tex Live in Windows. That is what is > written in the aucteX-menu, at least. What I also noticed: Contrary to wsl, > in cygwin there no teX-related lines at all in .emacs. - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITT UND KOMFORT - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Ikumi, > Do you mean that only a single "#" appeared in the echo area? Not > "#"? And didn't emacs signal an error? Oops, pardon me, rest of the line in > my posting got swallowed up; "#" is what I get, you are correct. > Hmm... What happens when you issue the following command on the wsl bash > console? (not in emacs) > bash -c "tex.exe --version" & This: [1] 21 TeX 3.141592653 (TeX Live > 2022) kpathsea version 6.3.4 Copyright 2022 D.E. Knuth. There is NO warranty. Redistribution of this software is covered by the terms of both the TeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the TeX source. Primary author of TeX: D.E. Knuth. Which probably just confirms that Tex Live is no unknown entity to wsl, only wsl-emacs/ aucteX still seem reluctant to communicate. I just got another idea. Before switching wsl, I had emacs/ aucteX succesfully running 'out-of-the box' under cygwin. Were this not comparable conditions, .i.e. a subsystem in which emacs/ aucteX had to fetch the pdflatex.exe in Tex Live in Windows. So, maybe it could be helpful to reinstall that again and compare entries in corresponding .init- or .emacs files? - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Pete, > petepetit...@my.mail.de writes: > Greetings Ikumi, > 1. No helloworld.pdf has been generated after the procedure. I see. Then pdflatex didn't run actually. > 2. C-x C-e brings up: > (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option > "ls") Desktop '#*message*-20220824-044008#' [...] > So no helloworld.pdf, the corresponding pdfs of the other tex-files > have been sucessfully generated via pdflatex.exe in the wsl-debian > console; apologies for the mess at home, btw. OK. > 3. This time C-x C-e was less verbose and just brought up this in > mini-buffer: # > Hopefully, I followed your instructions correctly. Do you mean that only a single "#" appeared in the echo area? Not "#"? And didn't emacs signal an error? Hmm... What happens when you issue the following command on the wsl bash console? (not in emacs) bash -c "tex.exe --version" & Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Greetings Ikumi, 1. No helloworld.pdf has been generated after the procedure. 2. C-x C-e brings up: (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option "ls") Desktop '#*message*-20220824-044008#' Documents Music Downloads newest.tex getorg.aux News getorg.log new.tex '#getorg.org#' new.tex~ getorg.out Pictures getorg.pdf Public getorg.synctex.gz _region_.tex getorg.tex sent getorg.tex~ Templates getorg.toc testat.aux '#helloworld.tex#' testat.log helloworld.tex testat.pdf hellworld.tex testat.tex mail test.aux '#*message*-20220730-045537#' test.log '#*message*-20220730-054520#' test.pdf~ '#*message*-20220730-054836#' '#test.tex#' '#*message*-20220730-055337#' test.tex '#*message*-20220730-060511#' test.tex~ '#*message*-20220730-063003#' '#texnochmaltest.tex#' '*message*-20220730-063003' texnochmaltest.tex '*message*-20220801-160735' texnochmaltest.tex~ '#*message*-20220824-032856#' texput.log '#*message*-20220824-034534#' Videos So no helloworld.pdf, the corresponding pdfs of the other tex-files have been sucessfully generated via pdflatex.exe in the wsl-debian console; apologies for the mess at home, btw. (Maria Kondo comes to mind ;-) ) 3. This time C-x C-e was less verbose and just brought up this in mini-buffer: # Hopefully, I followed your instructions correctly. (4.) Thank you for the valuable hint regarding other binaries; I will definitely have to adapt those as well, as instructed by you. Best regards and thank you very much again for your kind and patient assistance, Pete - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Keita, Ikumi Keita writes: > I'm talking about the situation when the command is called through wsl > bash shell. Bash is just a linux binary, so I suspect that it wouldn't > add suffix ".exe" implicitly when it searches executable file in PATH. > If there is only "pdflatex.exe" in PATH and no "pdflatex" (without the > suffix), I guess that bash would insist that "there is no executable > named pdflatex in PATH", ending up with invoking nothing. I've never used WSL, but you're right with your assumption[1]: Run Windows tools from Linux WSL can run Windows tools directly from the WSL command line using [tool-name].exe. For example, notepad.exe. [...] Windows tools must include the file extension, match the file case, and be executable. Non-executables including batch scripts. CMD native commands like dir can be run with cmd.exe /C command. Best, Arash Footnotes: [1] https://docs.microsoft.com/en-us/windows/wsl/filesystems#run-windows-tools-from-linux
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Joost, > Joost Kremers writes: > On Tue, Aug 23 2022, Ikumi Keita wrote: >> If the above guess is correct, you have to set at least `TeX-command' >> and `LaTeX-command' to "tex.exe" and "latex.exe" respectively > I don't use Windows or WSL myself either, but ISTR from the time that > I did use Windows occasionally, it would accept `latex` as command > invocation, even if the binary is called `latex.exe`. I think you are talking about the situation when you enter commands in windows command prompt (cmd.exe) or power shell. In that case, I agree that the suffix ".exe" can be omitted. I'm talking about the situation when the command is called through wsl bash shell. Bash is just a linux binary, so I suspect that it wouldn't add suffix ".exe" implicitly when it searches executable file in PATH. If there is only "pdflatex.exe" in PATH and no "pdflatex" (without the suffix), I guess that bash would insist that "there is no executable named pdflatex in PATH", ending up with invoking nothing. Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Hi Pete,
> petepetit...@my.mail.de writes:
>> Maybe the >output of `M-x TeX-submit-bug-report RET' would be helpful.
> I hope I have done this correctly: This is what I get with my default
> setup under which auctex can not find Tex Live in windows when I try
> to compile 'helloworld.tex'
Thanks, now I can confirm that your emacs thinks that it's running on
linux.
> This seems to have evoked something: Now, when loading helloworld.tex
> and run 'latex'-command
> 1) auctex does not complain any more but seems to be compiling.
> 2) asks to "Type 'C-c C-l" to display results of compilation"
OK. (More precisely, "Type ... compilation" isn't a request, so you
don't have to obey it. It's just an informative message to tell that
"you can do this".)
> Unfortunately though, this produces another error: 'Running `LaTeX' on
> `helloworld' with ``pdflatex.exe -file-line-error
> -interaction=nonstopmode helloworld.tex'''
That isn't an error. It indicates that AUCTeX did (try to) start
typeset. Under normal circumstances, it's followed by log message from
running pdflatex process like this:
--
Running `LaTeX' on `abc' with ``pdflatex -file-line-error
-interaction=nonstopmode abc.tex''
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022) (preloaded
format=pdflatex)
restricted \write18 enabled.
...
--
> Any idea what this might mean?
We have to find out the reason why log output didn't appear.
1. Was helloworld.pdf generated after the above procedure? If so,
pdflatex process did run successfully while emacs just fails to
capture its output.
2. After AUCTeX is loaded, insert
(start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option "ls")
at last of *scratch* buffer and type C-x C-e just after the closing
")". What appears in the buffer?
3. Try
(start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option
"tex.exe --version")
in the same manner and report the result.
By the way, if you need other binaries in TeX Live, e.g. bibtex,
makeindex etc., you have to modify the respective entries in
`TeX-command-list' to add ".exe" suffix like this:
> ("BibTeX" "bibtex %(O?aux)" TeX-run-BibTeX nil
("BibTeX" "bibtex.exe %(O?aux)" TeX-run-BibTeX nil
Use `M-x customize-option TeX-command-list RET' to do that.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
Re: AUCTex in WSL cannot find TeX Live in Win
Greetings Ikumi, First of all, thank you very much for the kind reply, really
appreciate it. Maybe this wsl-setup is just a little bit exotic and tricky,
especially for a beginner.
> Maybe the >output of `M-x TeX-submit-bug-report RET' would be helpful. I
> hope I have done this correctly: This is what I get with my default setup
> under which auctex can not find Tex Live in windows when I try to compile
> 'helloworld.tex' Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, X
> toolkit, Xaw3d scroll bars)
of 2021-03-28, modified by Debian
Package: 13.1.3 current state:
==
(setq
AUCTeX-date "2022-04-16"
window-system 'x
LaTeX-version "2e"
TeX-style-path '("~/.emacs.d/auctex"
"/home/citizen13/.emacs.d/elpa/auctex-13.1.3/style"
"/home/citizen13/.emacs.d/auctex/auto"
"/home/citizen13/.emacs.d/auctex/style" "auto" "style")
TeX-auto-save nil
TeX-parse-self nil
TeX-master t
TeX-command-list '(("TeX"
"%(PDF)%(tex) %(file-line-error) %`%(extraopts) %S%(PDFout)%(mode)%'
%(output-dir) %t"
TeX-run-TeX nil
(plain-tex-mode texinfo-mode ams-tex-mode) :help
"Run plain TeX")
("LaTeX" "%`%l%(mode)%' %T" TeX-run-TeX nil
(latex-mode doctex-mode) :help "Run LaTeX")
("Makeinfo" "makeinfo %(extraopts) %(o-dir) %t"
TeX-run-compile nil (texinfo-mode) :help
"Run Makeinfo with Info output")
("Makeinfo HTML"
"makeinfo %(extraopts) %(o-dir) --html %t"
TeX-run-compile nil (texinfo-mode) :help
"Run Makeinfo with HTML output")
("AmSTeX"
"amstex %(PDFout) %`%(extraopts) %S%(mode)%' %(output-dir) %t"
TeX-run-TeX nil (ams-tex-mode) :help "Run AMSTeX")
("ConTeXt"
"%(cntxcom) --once --texutil %(extraopts) %(execopts)%t"
TeX-run-TeX nil (context-mode) :help "Run ConTeXt once")
("ConTeXt Full" "%(cntxcom) %(extraopts) %(execopts)%t"
TeX-run-TeX nil (context-mode) :help
"Run ConTeXt until completion")
("BibTeX" "bibtex %(O?aux)" TeX-run-BibTeX nil
(plain-tex-mode latex-mode doctex-mode context-mode
texinfo-mode ams-tex-mode)
:help "Run BibTeX")
("Biber" "biber %(output-dir) %s" TeX-run-Biber nil
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Run Biber")
("Texindex" "texindex %s.??" TeX-run-command nil
(texinfo-mode) :help "Run Texindex")
("Texi2dvi" "%(PDF)texi2dvi %t" TeX-run-command nil
(texinfo-mode) :help "Run Texi2dvi or Texi2pdf")
("View" "%V" TeX-run-discard-or-function t t :help
"Run Viewer")
("Print" "%p" TeX-run-command t t :help "Print the file")
("Queue" "%q" TeX-run-background nil t :help
"View the printer queue" :visible TeX-queue-command)
("File" "%(o?)dvips %d -o %f " TeX-run-dvips t
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Generate PostScript file")
("Dvips" "%(o?)dvips %d -o %f " TeX-run-dvips nil
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Convert DVI file to PostScript")
("Dvipdfmx" "dvipdfmx -o %(O?pdf) %d" TeX-run-dvipdfmx nil
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Convert DVI file to PDF with dvipdfmx")
("Ps2pdf" "ps2pdf %f %(O?pdf)" TeX-run-ps2pdf nil
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Convert PostScript file to PDF")
("Glossaries" "makeglossaries %(d-dir) %s" TeX-run-command
nil
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Run makeglossaries to create glossary file")
("Index" "makeindex %(O?idx)" TeX-run-index nil
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Run makeindex to create index file")
("upMendex" "upmendex %(O?idx)" TeX-run-index t
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Run upmendex to create index file")
("Xindy" "texindy %s" TeX-run-command nil
(plain-tex-mode latex-mode doctex-mode texinfo-mode
ams-tex-mode)
:help "Run xindy to create index file")
("Check" "lacheck %s" TeX-run-compile nil (latex-mode)
:help "Check LaTeX file for correctness")
("ChkTeX" "chktex -v6 %s" TeX-run-compile nil (latex-mode)
:help "Check LaTeX file for common mistakes")
("Spell" "(TeX-ispell-document \"\")" TeX-run-function nil
t :help "Spell-check the document")
("Clean" "TeX-clean" TeX-run-function nil t :help
"Delete generated intermediate files")
("Clean All" "(TeX-clean t)" TeX-run-function nil t :help
"Delete generated intermediate and output files")
("Other" "" TeX-run-command t t :help
"Run an arbitrary command")
)
> you have to set at least `TeX-command'
> and `LaTeX-command' to "tex.exe" and "latex.exe" respectively (without
> "pdf" prepended). Try inserting
> (setq TeX-command "tex.exe"
> LaTeX-command "latex.exe")
> in your personal init file. (Or you can use customize interface using
> `M-x customize-option RET TeX-command RET' and `M-x customize-option RET
> LaTeX-command RET')
> However, I'm not sure whether those treatments are enough or not.
I did as proposed by you and opted for writing (setq TeX-command "tex.exe"
LaTeX-command "latex.exe") into my .emacsGood news first: This seems to
have evoked something: Now, when
Re: AUCTex in WSL cannot find TeX Live in Win
Greetings Sivaram, Thank you for trying to help! M-x getenv RET PATH in wsl-emacs lists the mounted windows-path of Tex Live as /mnt/c/texlive/2022/bin/win32/ To make sure, I also included: /mnt/c/texlive/2022/bin/win32/pdflatex.exe Best regards, Pete Am 23-Aug-2022 19:26:54 +0200 schrieb nsivaram@gmail.com: On Mon, Aug 22 2022,petepetit...@my.mail.de nil wrote: > Hi, [snipped 68 lines] > > Nobody knows? In the auctex-command settings I've tried by changing command > 'pdflatex' to 'pdflatex.exe', but auctex still can not find TexLive. > > Maybe I have to give and/ or mount the full Windows TexLive somehow, > somewhere? > What does M-x getenv RET PATH show within wsl-emacs? Does it have all the windows paths you want? sivaram -- - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT
Re: AUCTex in WSL cannot find TeX Live in Win
On Tue, Aug 23 2022, Ikumi Keita wrote: > If the above guess is correct, you have to set at least `TeX-command' > and `LaTeX-command' to "tex.exe" and "latex.exe" respectively I don't use Windows or WSL myself either, but ISTR from the time that I did use Windows occasionally, it would accept `latex` as command invocation, even if the binary is called `latex.exe`. -- Joost Kremers Life has its moments
Re: AUCTex in WSL cannot find TeX Live in Win
On Mon, Aug 22 2022,petepetit...@my.mail.de nil wrote: > Hi, [snipped 68 lines] > > Nobody knows? In the auctex-command settings I've tried by changing command > 'pdflatex' to 'pdflatex.exe', but auctex still can not find TexLive. > > Maybe I have to give and/ or mount the full Windows TexLive somehow, > somewhere? > What does M-x getenv RET PATH show within wsl-emacs? Does it have all the windows paths you want? sivaram --
Re: AUCTex in WSL cannot find TeX Live in Win
Hi petepetite75, > petepetit...@my.mail.de writes: > AUCTex in WSL cannot find TeX Live in Win When trying to compile/ > pdf-preview a tex-file, minibuffer spits out: > ERROR: AUCTeX cannot find a working TeX distribution. Make sure you have one > and that TeX binaries are in PATH environment variable I don't use wsl, so I'm not at all confident with this issue. Maybe the output of `M-x TeX-submit-bug-report RET' would be helpful. > When I tell auctex in wsl-emacs to compile/ 'pdflatex' helloworld.tex, > it by default tries to do this within _wsl_. So it is bound to > complain, as there is no TexLive in wsl. > The right and as we've seen above working command to compile/ > 'pdflatex' the file in TexLive _Windows_ is pdflatex._EXE_. > So it seems all I would have to do is tell auctex to execute > pdflatex.exe, instead of just pdflatex. Currently that seems most probable for me. I guess your emacs thinks that it's running on linux, and sets up `TeX-shell' to bash. And I guess that wsl bash needs ".exe" to run windows binaries on the PATH. > Does this make any sense? If so: now how/ where in auctex can I change > the default command accordingly? If the above guess is correct, you have to set at least `TeX-command' and `LaTeX-command' to "tex.exe" and "latex.exe" respectively (without "pdf" prepended). Try inserting (setq TeX-command "tex.exe" LaTeX-command "latex.exe") in your personal init file. (Or you can use customize interface using `M-x customize-option RET TeX-command RET' and `M-x customize-option RET LaTeX-command RET') However, I'm not sure whether those treatments are enough or not. Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
