You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your Windows build number: (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.15063]
I have two ways to launch emacs in WSL. The first one is by runemacs.exe and the second by XRun.vbs; more details -- Tips for emacs . I found it cannot run powershell in the second one.
The key of the first one is to create process C:\Windows\System32\"bash.exe" -l -c emacs by C code and executable file. When emacs is launched, it sit like this; init---init---emacs like "init---init---bash" of "bash.exe ~ -l".
The key of the second one is to execute shell application "bash.exe" with "-c 'export DISPLAY=:0; emacs&'&" argument by Visual Basic Script and "emacs&" argument; there are two &s, the first one was "emacs&" for launch emacs in background and the second "'export DISPLAY=:0; emacs&'&" for bash, but I think those are irrelevant. When emacs is launched, it sit like this; init---emacs like "init---bash" of "bash.exe ~".
The difference looks middle init between init---init---emacs and init---emacs.
I found browse-url-edge elisp function hang, so tested to run "/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe" in shell mode, M-x shell, and it hang in the second, i.e., init---emacs. Of course, it will not hang in "init---bash" but hang in "init---emacs".
I want to the concept of "bash -c 'some commands block'&", so inserted "-l" option, to hope middle init, but in vain.
This discussion was converted from issue #2065 on October 05, 2020 21:28.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
ver
at a Windows Command Prompt)Microsoft Windows [Version 10.0.15063]
I have two ways to launch emacs in WSL. The first one is by runemacs.exe and the second by XRun.vbs; more details -- Tips for emacs . I found it cannot run powershell in the second one.
The key of the first one is to create process
C:\Windows\System32\"bash.exe" -l -c emacs
by C code and executable file. When emacs is launched, it sit like this;init---init---emacs
like "init---init---bash" of "bash.exe ~ -l".The key of the second one is to execute shell application
"bash.exe"
with"-c 'export DISPLAY=:0; emacs&'&"
argument by Visual Basic Script and "emacs&" argument; there are two &s, the first one was "emacs&" for launch emacs in background and the second "'export DISPLAY=:0; emacs&'&" for bash, but I think those are irrelevant. When emacs is launched, it sit like this;init---emacs
like "init---bash" of "bash.exe ~".The difference looks middle
init
betweeninit---init---emacs
andinit---emacs
.I found browse-url-edge elisp function hang, so tested to run "/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe" in shell mode, M-x shell, and it hang in the second, i.e.,
init---emacs
. Of course, it will not hang in "init---bash" but hang in "init---emacs".I want to the concept of "bash -c 'some commands block'&", so inserted "-l" option, to hope middle init, but in vain.
Beta Was this translation helpful? Give feedback.
All reactions