Skip to main content

Emacs on WSL2: From Monochrome Misery to Modern Elegance

Windows Subsystem for Linux (WSL) has come a long way—especially under Windows 11. WSL2 now offers smooth integration for Linux graphical applications, making it feel less like a compatibility layer and more like a native experience. But if you're an Emacs user, you might have noticed something off.

Launching Emacs under WSL can feel like stepping into a time machine. Tiny fonts, washed-out visuals, and a UI that evokes the green-and-amber glow of vintage terminals. Functional? Yes. Pleasant? Absolutely not.

But here's the good news: it is easy to make Emacs under WSL2 look just as sharp and modern as it does on Mac OSX.

The emacs-pgtk build is designed for better graphical integration under WSL. It uses the Pure GTK interface, which plays nicely with WSL’s GUI support.

sudo apt install emacs-pgtk

To make Emacs look great, we’ll use Windows’ rich font library. First, edit your font configuration:

sudo emacs /etc/fonts/fonts.conf

and add the Windows Font directory to the list of font directories:

<dir>/mnt/c/Windows/Fonts</dir>

This tells Ubuntu to include Windows' TrueType fonts in its font cache.

Then we refresh the font cache:

fc-cache -fv

And finally start Emacs, and in the font selection popup, you should see all your favorite Windows fonts. I went with Consolas 14pt, and the transformation was instant. Crisp text, modern aesthetics, and no more squinting.

Labels:

Comments

Post a Comment

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...
2 comments
Read more

A paper a day keeps the dr away: Dapper a Large-Scale Distributed Systems Tracing Infrastructure

Modern Internet scale applications are a challenge to monitor and diagnose. The applications are usually comprised of complex distributed systems that are built by multiple teams, sometimes using different languages and technologies. When one component fails or misbehaves, it becomes a nightmare to figure out what went wrong and where. Monitoring and tracing systems aim to make that problem a bit more tractable, and Dapper, a system by Google for large scale distributed systems tracing is one such system. The paper starts by setting the context for Dapper through the use of a real service: "universal search". In universal search, the user types in a query that gets federated to multiple search backends such as web search, image search, local search, video search, news search, as well as advertising systems to display ads. The results are then combined and presented back to the user. Thousands of machines could be involved in returning that result, and any poor p...
Post a Comment
Read more

A paper a day keeps the doctor away: MillWheel: Fault-Tolerant Stream Processing at Internet Scale

The recent data explosion, and the increase in appetite for fast results spurred a lot of interest in low-latency data processing systems. One such system is MillWheel, presented in the paper " MillWheel: Fault-Tolerant Stream Processing at Internet Scale ", which is widely used at Google. In MillWheel, the users specify a directed computation graph that describe what they would like to do, and write application code that runs on each individual node in the graph. The system takes care of managing the flow of data within the graph, persisting the state of the computation, and handling any failures that occur, relieving the users from that burden. MillWheel exposes an API for record processing, that handles each record in an idempotent fashion, with an exactly once delivery semantics. The system checkpoints progress with a fine granularity, removing the need to buffer data between external senders. The authors describe the system using the Zeitgeist produ...
Post a Comment
Read more