Doom

As shown under another article, I’m using uvx to run some mcp servers needed by mcp.el. However, when I first started them on NixOS, I encountered an error. After consulting Gemini for solutions and a root cause analysis, here are my notes. Symptoms and Error Message Checking the *Mcp-Hub/ buffer with mcp-hub-view-log, the following error appeared: [stderr] Could not start dynamically linked executable: /home/bk/.cache/uv/archive-v0/unI5q9QapqXHm9fPXna4G/bin/python [stderr] NixOS cannot run dynamically linked executables intended for generic [stderr] linux environments out of the box. For more information, see: [stderr] https://nix.dev/permalink/stub-ld [jsonrpc] D[14:56:49.461] Connection state change: `exited abnormally with code 127 Solution: Enable nix-ld Adding the following to your nix configuration resolved the issue for me: ...

Introduction The integration of large language models (LLMs) into Emacs has rapidly evolved over the past few years. My first encounter with an LLM inside Emacs was in November 2022, through AI-powered code completion with copilot.el. I still vividly remember how impressed I was at that moment. Shortly after, ChatGPT was launched, and tools like ChatGPT.el made it possible to interact with AI within Emacs—though, at that time, the features were few, and I didn’t really feel the advantages of using LLMs in Emacs. ...

The Problem The other day, when I started Emacs as usual, the following message appeared in the minibuffer: Project <Project Name> at <Project Path> cannot be read. Emacs then became a piece of software that simply displayed a white screen. I had recently changed the path of this project, so I suspected that might be the cause. I tried modifying/deleting the project path in projectile-known-projects-file, but the situation didn’t improve. I also tried commands like doom sync and doom upgrade, but none of these resolved the issue. ...