Clojurians Log v2
emacs 2026-10-22
Some people told me a Claude pkg of mine can be useful so I've shared it publicly. Take a look if you're curious. The idea is simple. Just manage Claude sessions and interact with it via emacs by sending commands to tmux. One can always adapt to use eat, eshell or whatnot instead. The idea here is that if someone wants a base code to start off, one can just fork the project and start tweaking. https://github.com/danielhvs/daniel-claudy
Thanks! did you attempt any other interfaces into claude besides tmux, and this was what you found is the best setup for you? e.g. https://github.com/xenodium/agent-shell, i've been using claude + tmux, because i had a history of using tmux for a decade, but haven't really gone exploring for alternatives, maybe a waste of time though (?). -- Also i can never decide if i want to run emacs inside tmux in terminal mode, or outside as GUI... perpetually non-decisiveness here.
Hello. Yeah, the thing is I have a history behind it since I used vim + tmux for a long time. Then when I migrated to emacs kept some of the workflows with tmux. "Before AI" I developed a flow in which I send cmds to tmux via emacs with some kbds like -tq etc. Then since claude code works well in the terminal I (aka me + claude) developed slowly a workflow for me to read the claude transcripts inside emacs (reading from claude internal files) and sending commands to tmux from emacs (sameish flow from before). I think tmux is nice because I can spawn multiple sessions but of course today there is herdr and stuff. I use emacs as a GUI always and just sometimes, when I need to, send cmds to tmux but my usages are only for 2 purposes mainly: 1. claude 2. When i need to ssh to a server and do stuff and i have some pre-made stuff I need to send With i3 in place I have a pretty straightforward workflow to switch back and forth to the terminal (tmux) and emacs: workspace 1: emacs workspace 2: firefox workspace 3: brave-browser workspace 4: terminal (tmux)
Why not use ghostel in Emacs? It covers most of my uses of terminal. I also have Kitty and sometimes I want to run a command in "detached mode" through remote-protocol - so the long-running process doesn't prevent me from e.g., restarting Emacs. When I need to pipe things in and out of Emacs buffers I use the piper https://github.com/agzam/mxp
Ah! Nice to know about ghostel. That's interesting. Will take a look into it. Thanks for sharing, @ag
I think that's the last real big decision left... (if you want a unified setup) its either 1. ghostty inside emacs (ghostel), 2. emacs [inside tmux] inside ghostty (emacs -nw) ... one of those two options is the best setup, there's no real other contenders in the shell or editor space 😉
I also have Kitty and sometimes I want to run a command in "detached mode" through remote-protocol -You could also just have Emacs control tmux, and treat ghostel as a tmux 'viewer'. Won't lose any [long running] processes. Many ways to make this burrito.
You could also just have Emacs control tmuxYeah, I know, I run E2Es this way, through an agent, which uses tmux socket. When my tests can't be done purely deterministically and I have to sandwich them between stochastic and deterministic layers.
Any recommendations for an Emacs plugin that supports https://www.conventionalcommits.org/ standard for commit messages? The plugin would provide completion of the conventional commit form or a popup form to create the commit message (allowing selection of types, scopes, etc). Bonus points if the plugin also supports emojis in the description. Ideally the plugin is available through Melpa, Elpa, etc.
I found https://github.com/akirak/conventional-commit.el but it was never packaged and had no updates for many years.