Trying to make emacs into VS Code in 2025 is as stupid as trying to make emacs into eclipse in 2005 or notepad in 1985.
Or if you don't feel like learning the details, go with doom.
But the manual is very well written and worth the read. Emacs has its own culture, and the sooner you learn the conventions, the smoother your path will be.
Pretty sure they mean something that at least involves use-package, vertico/consult/etc. or equivalent, company or corfu, project.el or projectile, and magit.
> You can start with a minimal config like Emacs Bedrock or Prelude, and then learn about those options first.
Prelude seems nice but I wouldn’t call it minimal unless you’re comparing to Doom and Spacemacs.
Elisp is a programming language that supports many ways to do things so there is lots of ways people do things.
More precisely, as I understand it, “genie" is an anglicization of its Arabic equivalent, “jinn"; Efrit is a specific kind of jinn.
(I use the past tense, because Emigo has not been updated in a quarter of a year, which seems as if it may as well be decades in the timeline of this sort of stuff.)
(use-package efrit
:quelpa (efrit :fetcher git :repo "steveyegge/efrit")
:init
(setq efrit-model "gemini-2.5-pro")
;; (setq efrit-api-url "https://generativelanguage.googleapis.com/v1beta/opena
(setq efrit-api-url "http://127.0.0.1:8089/v1/messages")
:config (defun efrit--get-api-key () (key-from-file "~/.keys/gemini.txt")) ; this isn't needed, it's set by the proxy
:ensure t)
I needed to remove the uvicorn version constraint when importing the project to uv to get it to find a version solution.Initially I thought you could send it directly to Gemini but apparently you need to proxy and translate the responses.
[1] Seems sketchy, use at your risk: https://github.com/coffeegrind123/gemini-for-claude-code
It's terrible at multi-step tasks right now. I'm evolving it to work more like claude code.
But, I cannot seem to get past this error when I run claude-code-ide: "Symbol’s function definition is void: project-root" I know this is defined in project.el, but claude has been surprisingly unhelpful at fixing this issue.
I'm feeling a bit frustrated by the state of emacs packages lately. I've used emacs for 30 years and it feels like things are getting worse.
I'm more than happy to work with you to get it working, with the caveat that it actually kind of sucks right now. It's no Claude Code. But I am quickly evolving it in that direction.
This is turn 4. Focus on any remaining tasks that haven't been completed yet. Don't repeat work that was already done in previous turns.
Assistant: I notice from the context that we're in a directory that might be related to a xxx project. Let me try to find and open the yyyy.ts file.
[Result: Error: Unknown tool 'resolve_path']
I'm working on evolving it into something that's not so transactional -- it will work more like claude code. Didn't realize it was going to hit the front page today. I'll poke at it this weekend and send an update.
After reading your wikipedia page, I didn't realize we were both at UWash CS at the same time. Small world.
Claude is remarkably effective at writing elisp I surprisingly found. I had it whip up a mode today for something today (Notation3/N3 RDF triples) complete with etags support, etc. and it just... did it.