# Emacs

I tend to use Emacs with *evil-mode* for any kind of extended editing and programming, unless I'm using an IDE (with a Vim plugin of course!) in the latter case.

One of the disadvantages of evil-mode is that there's a high chance that advanced commands *might* not as expected in Emacs. For example, `:normal ...` commands do not work in evil-mode. Also Vim regex and Emacs regex are not really compatible - so your Vim regex know-how will not translate directly to Emacs. So, when it comes to raw editing Vim probably is the better editor from my experience.

However, with evil-mode one can easily use Emacs editing functionality as well which comes with the downside of haing to learn two disparate kind of editing paradigmns.

## Configuration distributions

### Spacemacs

This is what I have been using for a couple of years and I would recommend this someome wanting to transition from Vim to an Emacs workflow.

### [Doom Emacs](https://github.com/dewaka/wiki/tree/d44d1d2fd0ecdfa632746dee860379a151a94828/text-editors/emacs/doom.md)

I have been trying this configuration package recently and I am quite impressed with the low startup overhead of the Doom configuration.

### Blogs

* [Xah Emacs Blog](http://ergoemacs.org/emacs/blog.html)
* [Emacs Rocks](http://emacsrocks.com/)
* [Sacha Chua - Emacs](https://sachachua.com/blog/category/emacs/) - Sacha's

  blog has a treasure trove of Emacs knowledge both written by herself and

  aggregated links.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.dewaka.com/editors/emacs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.