<p>As posted in a few places, <a href="https://lists.gnu.org/archive/html/emacs-devel/2018-04/msg00258.html">Emacs 26.1-RC1 has been released</a>. Following up my <a href="https://www.lonecpluspluscoder.com/2017/11/15/emacs-on-the-linux-subsystem-for-windows/">previous experiments with running Emacs on the Windows Subsystem for Linux</a>, I naturally had to see how the latest version would work out. For that, I built the RC1 on an up-to-date Ubuntu WSL. I actually built it twice – once…

<p>A quick follow-up to my <a href="https://www.lonecpluspluscoder.com/2017/12/13/running-emacs-inside-emacs/">last post where I was experimenting with running emacsclient from an ansi-term</a> running in the main Emacs. Interestingly, you can run Emacs in text mode within an ansi-term, just not emacsclient:</p>

<p>I’m experimenting with screen recordings at the moment and just out of curiosity decided to see if I can load and edit a text file inside the main Emacs process from inside an ansi-term using emacsclient.</p>

<p>I’ve had the Linux Subsystem for Windows enabled for quite a while during the time it was in Beta. With the release of the Fall Creators Update, I ended up redoing my setup from scratch. As usual I grabbed Emacs and a bunch of other packages and was initially disappointed that I was looking at a text-mode only Emacs. That might have something to do with the lack of an X Server…</p>

<p>Emacs 25.3 has been <a href="https://lists.gnu.org/archive/html/info-gnu/2017-09/msg00006.html">released</a> on Monday. Given that it’s a security fix I’m downloading the source as I write this. If you’re using the latest Emacs I’d recommend you update your Emacs. The vulnerability as been around since Emacs 19.29, you probably want to upgrade anyway.</p>