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
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
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
> 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
> 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
> 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
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
> 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.
>
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
> 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
> 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
> 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]
> 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
> 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
> 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
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
> 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
> 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
> 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
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
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
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
> 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
>>
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
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
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
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,
> 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
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
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 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
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
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'
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:
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
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
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
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
40 matches
Mail list logo
