[BaculumMeumEst]

gptel is great because it does exactly what you would expect and stays up to date with new models from anthropic and openai. Before settling on gptel, I went through FOUR programs that had a lot of buzz but were not being kept up to date with new models!

gptel has joined magit and undo-tree in being so damn useful and reliable that they are keeping me from ditching emacs, even though I want to.

[__mharrison__]

Mentioning that it is on par with magit is a strong recommendation. Going to try this out tomorrow.

[marci]

Gptel leverages Magit's interface.

[johanvts]

Yes, its called transient and it’s pretty simple to use for your own projects. I wrote a transient for my work tasks and now ex. Creating a new youtrack issue is effortless.

[ossusermivami]

it's built-in emacs as well now!

[nanna]

Personally I ditched undo-tree for Vundo (visual undo), which has all the functionality that I need from undo-tree whilst being significantly lighter. Give it a spin!

https://github.com/casouri/vundo

[jasonm23]

It's kmacros, wgrep (with ripgrep) and wdired that keep me using it....

VSCode / VSCodium have really pulled me away from it a lot this year though, after ~30 years.

[BaculumMeumEst]

Yeah, I like a lot about VS code and it feels far less annoying to use. It just sucks that there's no undo equivalent to undo-tree, the Git equivalents are not up to snuff (I just end up using CLI, which is fine I guess). But gptel is also super useful, and there's no good VS code equivalent I've found for that either.

wgrep is nice, I use it very rarely but its useful. I did not know about wdired, looking that up now, looks very cool, you are NOT helping me escape this damned editor..

[PestoDiRucola]

May I ask why do you want to ditch emacs and in favor of what?

[autumn-antlers]

Not OP, but I feel strongly about this.

I've got a lot of Lisp experience, and love Emacs' values and ecosystem. I still use neovim regularly because of a tangle security, a sound sure-footedness of action, derived from consistency and latency. It takes a combination of confident action on the users part and confident response from the machine to perpetuate the user's experience of both speed and intrusive confidence. (IMO) Emacs fails to deliver this experience plainly in latency due to the main thread blocking (even with more the 8MB of RAM). It fails partly due to the greater variety of modes and (as an evil user) lack of "core" support for Vim bindings, creating a higher sense of care and vigilance, but I really that could be over-come if one's config is kept small and the ecosystem tuned more towards robustness and optimization in visible UI, tactile UI, and multi-threading.

In favor of what, I don't know. Something that explicitly aspires to feature-parity with a modern-emacs stack (vertico/corfu/marginalia/transient/tramp), but which sacrifices some aspect of the platform's flexibility (eg. make plugins use transient and allow consistent global user prefs) to prioritize consistency, latency, and robustness for the sake of UX.