Amazing in native Windows 11's Emacs28.1 to get Linux environment as shell-command and interactive shell

It's amazing to run everything with Linux within Emacs 28.1 of native wins version, but just need two lines of codes: (setq shell-file-name "C:/Windows/system32/bash.exe") (setenv "ESHELL" "bash") 1. Then you could get a bash shell of wsl-linux after M-x shell: https://preview.redd.it/xjjcj2wmh7v81.png?width=913&format=png&auto=webp&s=9d4d5e7f37e53e609331a281cc13fae156645836 2. Invoke shell-command(M-!) in bash environment rather than cmd.exe: https://preview.redd.it/9mv9hnrri7v81.png?width=814&format=png&auto=webp&s=f125a946a340bcd80bff12d77892f827ef9f1f43 Yeah, cmd.exe environment gone. you can comfortable run "git add .; git commit -m 'comment'; git push" now in bash environment. ​ 3. Also surprising to find the any 'commands' bind to ones of wsl-linux, grep-find, counsel-rg for example: M-x grep-find (find . -type f -exec grep -nH -e 'shell-file-name' \{\} \;) https://preview.redd.it/6ctmjrcwj7v81.png?width=960&format=png&auto=webp&s=f0a6c0b4fe8b022a626fb9c8b16ea5d870b39b39 It's grep and find in wsl environment not ones of scoop in cmd.exe or powershell.exe, just surprising. ​ 4.Try counsel-rg to search Chinese characters https://preview.redd.it/z7xphhckk7v81.png?width=790&format=png&auto=webp&s=78386487066b3a544ff2123d324039badebcfe1e 5.Additional, Linux manuals works from M-x man： https://preview.redd.it/n1emg1ruk7v81.png?width=799&format=png&auto=webp&s=9f9104f4e66fe32d350b0b28047e7bac787dbc0d 6. Open other windows native apps from Emacs with M-& (async-shell-command) . https://preview.redd.it/yleomzo1m7v81.png?width=954&format=png&auto=webp&s=d3fef69f54db8e4942f2643de56be9c3ad0954cc It works on 28.1 but fails in 27.2. Finally, babel-src block in org https://preview.redd.it/zpywf7aem7v81.png?width=777&format=png&auto=webp&s=7f61cb859698acb769bf3400920083b1fa57b437 Achieve all above functions, only two lines of codes in emacs 28.1 (setq shell-file-name "C:/Windows/system32/bash.exe") (setenv "ESHELL" "bash") Amazing. No needs of GWSL any more or VcxSrv or X410 desktop.

Watch out linux! there is a new kid coming after you!

exciting so much.

Than you. This is going to be one of the nicest productivity increases in my workflow.

Sure, productivity is taking off.

I'd rather just use Linux anyway...

What's WSL git on the windows file system like, performance wise?

The first step is letting it working.

This is awesome thanks! What is the audio player you’re using?

Glad to help, I use win11's default "Media Player", it was called "Groove Music" on Win10.

Is the filesystem performance issue fixed? Otherwise, it can't be used in lots of real projects.

woohooo!!!! THANK YOU SO MUCH!! this is already EPIC 😁

Windows now includes bash?

C:/Windows/system32/bash.exe invokes WSL.

Agreed :>

Ah, interesting to know. Is that by default?

>Yeah, cmd.exe environment gone. you can comfortable run "git add .; git commit -m 'comment'; git push" now in bash environment. But is it going to work with magit without extra configuration?

oh ok lol. i thought it was a module in emacs and was intrigued.

Magit is slow with both native windows emacs and wsl' emacs.

M-& explore.exe open file with default windows apps.

That's a shame, magit is a gamechanger for me

Not, until the fix the Forking Fork implementation on Windows.

You need to install WSL for it.

Ah good to know. That helps me know how much I can rely on that with companies that require Windows use.

Np. WSL 2 automatically releases unused RAM back to Windows, and on 11 lets you run graphical applications instead of just text shells (so you can then i.e. run Emacs from within WSL).

> WSL 2 automatically releases unused RAM back to Windows It has [memory ballooning](https://en.wikipedia.org/wiki/Memory_ballooning), that's nice.

Lol

Not sure if it's caused by the same thing you mentioned but 2 days ago I've tried to do some Unity development with Emacs on Windows and it was lagging too much to be usable. It still can't be used in real projects yeah, so Linux is the only option.

just tried it, any luck with the find-file ( C-x C-f ) command ?, when Im navigating through the directories in the bash shell and then try to open a file in the current directory, emacs does not position the current directory in the mini-buffer to the current directory in the bash shell, essential QOL.

most importantly, can you make pdftools work?

I tried and no problems with C-x C-f (ivy-package).

I assume it might better to open pdf with default "adobe reader pro" by M-& explore.exe some-book.pdf.

[deleted]

tested in [emcas 29](https://github.com/kiennq/emacs-build), `M-x shell` can run neofetch too.

It's as fast as a native Linux file system

WSL is Linux

If using WSL(1) it performs as well as a Windows native git.

/r/bashonubuntuonwindows

I just used pdf tools in WSL to merge 2 pdfs this week.

How about accessing windows native files? I tried it before, it's unacceptably slow.

Accessing Windows files with WSL1 is native, as fast as NTFS on Windows. NTFS has different performance for small file read/writes than ext4. If you are doing a task that has massive amounts of IO to the Windows file system then you should use WSL1. Often someone wants something compiled to exist in Windows, and uses WSL2 for a massive amount of small file io. It's important to remember that Windows can access WSL2 filesystems. So the correct sequence in making that available to Windows isn't to work there, but use the result stored or transferred from WSL2 directly from Windows. What exactly was your use case?

Why don't you post this over at /r/bashonubuntuonwindows

are you using wsl emacs with pdf-tools or the native windows emacs?

I'm testing this now on a windows machine and it doesn't seem to work for me. When I tried to open the man page for 'find' with 'man' I got "/bin/bash: line 1: NUL: Permission denied" Then I tried to grep my init.el for System, and I got an error 255. It seems emacs is sending a NUL to the program and that is causing an error. Here's the output, it had a lot more \\0 lines, but I abbreviated it: -*- mode: grep; default-directory: "~/.emacs.d/" -*- Grep started at Sun Apr 24 10:45:10 grep -n System init.el NUL \0 [...] \0 Grep exited abnormally with code 255 at Sun Apr 24 10:45:10

Everything is WSL. I don't often duplicate toolkits.

I have a project use win toolchain to compile ,but I want to use emacs and git to manage the source code in WSL.

Ok. Once synced git changes are generally small diffs on files. The overhead of using WSL would be negligible. Also, you would use WSL1, where there would be zero overhead. The only thing you would do, which isn't unique to WSL, is add exceptions to Defender to not scan your project folders so that when heavy IO happens there is no antivirus penalty. Or add a specific exception for Git. But, just to summarize, WSL1 would have no penalty regarding file access, and you can use Emacs and git.

One of the most depressing experiences I’ve had lately was finding out that even Magit on Linux over TRAMP is so much faster than Magit on Windows.

I haven't found magit to be "slow" on windows native emacs, but I do remove some time consuming sections: (remove-hook 'magit-status-sections-hook 'magit-insert-status-headers) (remove-hook 'magit-status-sections-hook 'magit-insert-stashes) (remove-hook 'magit-status-sections-hook 'magit-insert-tags-header) (remove-hook 'magit-status-sections-hook 'magit-insert-unpulled-from-upstream)

Unfortunately, I think the only one of those sections I *might* not find useful is the unpulled commits one, and even that helps to get my bearings.