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
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
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
Anfang der weitergeleiteten E-Mail
Von: petepetit...@my.mail.de
An: ik...@ikumi.que.jp
Datum: 24-Aug-2022 05:06:47 +0200
Betreff: 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
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:
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
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
> 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
> 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
> 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.
>
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
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
> 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
Hi, I have posted the persistant problem three weeks ago already to
https://emacs.stackexchange.com/questions/72860/auctex-in-wsl-cannot-find-tex-live-in-win,
but nobody seems to know the answer.I suspect the solution may be pretty
straightforward, but I'm just a emacs+ auctex beginner,
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
> 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
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
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
> 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
> 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
20 matches
Mail list logo
