51–60 of 92 posts
Earlier quoted context omitted.
I use cLaude cOde in my eMacs (through ghostel, which is unbelievably great!) to generate code :-) I then use mAgit to review it.
The iPhone autocorrects it to eMacs... it's so annoying.
Setting up a keyboard replacement is the way to go here. Solves the issue for all devices.
Uhm, no, I haven’t.
Why should I care if the Markdown mode uses Treesitter or not…? Does it affect the performance or UX somehow?
Earlier quoted context omitted.
I’m trying to use a similar workflow, but when I attempt to use Claude code in vterm, I have issues. My use case is resuming a session and not being able to scroll back to the past history. Otherwise if I start a new session, it works fine. It’s probably related to me being on an old version of vterm, but I’m just wondering if you ever have come across this.
Definitely try ghostel, it's really solid.
Ubuntu has a fair number of elpa packages in its repos, so I’m trying to make it work if possible. Not sure if I’m missing anything config wise within the confines of vterm
Earlier quoted context omitted.
I speak only for myself and not the Emacs team, but ... IMO it shouldn't do this by default - unless there is a clear "winner" among all the choices. IIRC, for eglot I had to install a Python language server. There are a bunch of them. Why would I want it to pick one by default? I don't know if Emacs will ever have an IDE with TS and LSP working "out of the box" without some configuration. From my experience with Egl…
Emacs makes many opinionated choices about defaults; if it didn't, it would launch to little more than an elisp REPL by default. What's important is that _you can change it_. Good defaults ensure that Emacs doesn't repel new users and casual users and users who are not interested in fiddling. And this isn't a matter of color theme default, or font default; this is a shipped feature that _does not function_ without ch…
I'm confused. Have things changed? The scratch buffer it starts with is for writing elisp.
> this is a shipped feature that _does not function_ without changes to the defaults!
Do you know how many shipped features come with Emacs that don't function without changes to defaults?
A huge number of them! Stuff like hippie-expand, ibuffer, etc. This isn't something new - it's been that way for decades.
> Good defaults ensure that Emacs doesn't repel new users and casual users and users who are not interested in fiddling.
This has been argued to death forever. While even I think they can and should change some defaults, the reality is that Emacs as an ecosystem is doing just fine without so many new/casual users, and will continue to do so. They don't want to be something for everyone.
And while I don't have the latest Emacs, in my experience with eglot - it's simply not ready for the masses. I frequently get timeouts, and would often have to shut down and restart eglot. It's been a while since I had to, so perhaps they've fixed all the issues, but it's simply not as robust as what you'd get with other IDEs. I'd rather they address those issues than the ease of use.
One of the biggest reason I've stopped using Emacs, and I was a pretty heavy user before was that org-mode files weren't fully native Markdown files, which caused annoying friction when collaborating with others. It would be interesting for me to have a new markdown-centric org-mode thing. I'd love to vibe lisp to customize my workflows, and I don't totally love Obsidian, which is what I've setup and configured now.…
I love Org-mode and use it for many things - the outline format is great, even for some unexpected cases - Jira tickets, Slack, Reddit and HN threads, etc. But of course, hard to escape Markdown these days, so I burned some tokens to implement this https://github.com/agzam/prisma.el
One of the biggest reason I've stopped using Emacs, and I was a pretty heavy user before was that org-mode files weren't fully native Markdown files, which caused annoying friction when collaborating with others. It would be interesting for me to have a new markdown-centric org-mode thing. I'd love to vibe lisp to customize my workflows, and I don't totally love Obsidian, which is what I've setup and configured now.…
Earlier quoted context omitted.
Tree sitter support is half baked in the same way official LSP support is, only kind of worse. Eglot won't help you get your system ready for LSP work, it will only avail itself if what's there. It doesn't even auto detect and configure that, either. There's no user prompting, so you'll have to read the docs to know that this even needs to be done. Similarly, tree sitter support doesn't include the grammars! And thos…
In Emacs 31 none of what you’re saying is true. Grammars auto install and setting them up is easy. https://www.reddit.com/r/emacs/comments/1utghab/treesitter_s...
Or I can do ESC enable-this-mode-option and then press a single key.
I'm struggling with this. If it's cheaper in keystrokes to type the codes inline why enable the mode?
This isn't a vi vs emacs hate thing, It's a key count efficiency thing. I don't see the motivation even if translated to minimum prefix TAB complete terms. Its like 20x more presses.
Earlier quoted context omitted.
I use windows 11, wsl2, WezTerm. emacs -nw directly on the shell. its like working on a linux computer, but from windows. I run vterm inside emacs, and claude code inside vterm. I have special commands for extracting file routes, and flow between dired and magit. Everything runs like magic. I also have copilot-chat and copilot-mode installed. From time to time I use it to review what claude has done, or to chat a lit…
I’m trying to use a similar workflow, but when I attempt to use Claude code in vterm, I have issues. My use case is resuming a session and not being able to scroll back to the past history. Otherwise if I start a new session, it works fine. It’s probably related to me being on an old version of vterm, but I’m just wondering if you ever have come across this.