/explore
|
You are here 
|
michaelneuper.com | ||
| | | | |
arenzana.org
Emacs > Visual Studio Code There's a good chance I'm a hater or that I don't know what I'm doing. After a couple of hours trying to set up VS Code for Rust development, I ended up frustrated not understanding how to simply call the compiler or the debugger from the interface. I looked for |
|
| | | | | ||
| | | | |
honnef.co
[AI summary] This article guides Emacs users through setting up and utilizing go-mode along with essential extensions like godef, goflymake, and auto-completion tools for efficient Go programming. |
|
| | | | | ||
| | | | |
v0dro.in
I'm writing this blog as I'm learning latex and setting up emacs to use it. Previously I mainly use LyX for writing research papers but the lack of text leads to lesser customization options sometimes, which is why I'll be shifting to plain text LaTeX henceforth. |
|
| | | | | ||
| | | | |
dht.is
SOLVED posts detail solutions to problems I could not find anywhere else. After installing axe-cli in my Ubuntu/Windows 11 environment using Windows Subsystem for Linux (WSL), I got the following error whenever I tried to run it: Chrome failed to start: crashed (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location [file path] is no longer running, so ChromeDriver is assuming that Chrome has crashed.) This can be caused by a lot of things (and I tried most of them), but in my case it was caused by Chrome not being installed in my WSL environment, which makes sense because I only use it for command line programs. |
|
| | | |||
