Closed umutzd closed 4 years ago
Are you using WSL1? The guide has not yet been updated to work with WSL2. If your are using WSL2 check out https://github.com/hubisan/emacs-wsl/issues/3.
Default terminal emulator wsl.exe?
Are you using the default terminal emulator that comes with WSL?
That's wsl.exe
at probably C:\Windows\System32\wsl.exe
?
What is the output of echo $TERM
? Is it xterm-256color
?
Emacs in Terminal working? Open WSL and run
emacs -nw -q
This should open Emacs in the terminal without loading your init.el.
Try without setsid and without loading the init file. Open WSL and run:
export DISPLAY=:0.0
emacs -q
@umucorn Were you able to solve your issue?
Hi, I solved this problem by following the instructions for WSL2. I was using WSL2.
But now, If I issue the command emacs
everything starts correctly.
Not when I run this:
alias eme='
export DISPLAY_NUMBER="0.0"
export DISPLAY=$(grep -m 1 nameserver /etc/resolv.conf | awk "{print $2}"):$DISPLAY_NUMBER
export LIBGL_ALWAYS_INDIRECT=1
setsid emacs
exit
'
I issue eme
command and everything disappears suddenly.
I solve this problem by changing eme
alias to this and moving exports anywhere else:
alias eme='
setsid emacs -q
exit
'
Hi, I solved this problem by following the instructions for WSL2. I was using WSL2.
Can you elaborate on which instructions you followed exactly? There are several options for each problem it seems.
I can't run emacs with either of the X Server software mentioned in the Readme file. Tried both of them, especially VcXsrv access disabled mode. I run them and I can confirm that they are running by looking at the task manager.
When I issue these commands:
The output is:
I don't know if there's anything to do with SSH or something else. I think I read it thoroughly.
Output of
uname -a
command: