doom-emacs VS magit

$ rm -rf ~/.config/emacs # Remove the existing directory if necessary git clone --depth 1 https://github.com/hlissner/doom-emacs ~/.config/emacs ~/.config/emacs/bin/doom install

Sounds like what you want is emacs, but preconfigured. In that case, have you tried Doom Emacs, Spacemacs or any of the myriad of others like those?

darren@pop-os:~$ git clone --depth 1 https://github.com/hlissner/doom-emacs ~/.emacs.d Cloning into '/home/darren/.emacs.d'... remote: Enumerating objects: 1156, done. remote: Counting objects: 100% (1156/1156), done. remote: Compressing objects: 100% (1042/1042), done. remote: Total 1156 (delta 85), reused 650 (delta 71), pack-reused 0 Receiving objects: 100% (1156/1156), 1.13 MiB | 7.29 MiB/s, done. Resolving deltas: 100% (85/85), done.

I used to do something like -{ nixosConfig, config, lib, pkgs, ... }: -let - xdgConfig = config.xdg.configHome; -in { - home.activation = { - foo = lib.hm.dag.entryAfter [ "writeBoundary" ] '' - doomdir="${xdgConfig}/doom"; - # $VERBOSE_ARG - if [ -d "$doomdir" ]; then - $DRY_RUN_CMD git -C "$doomdir" pull http master || true - else - # git clone and change url - http="https://git." - $DRY_RUN_CMD git clone "$http" "$doomdir" - # the new url needs ssh keys setup - git -C "$doomdir" remote add http "$http" - git -C "$doomdir" remote set-url origin "gitea@git." - fi - emacsdir="${xdgConfig}/emacs" - if [ -d "$emacsdir" ]; then - if [ -d "$emacsdir/.local" ]; then - $DRY_RUN_CMD $emacsdir/bin/doom sync - fi - else - $DRY_RUN_CMD git clone --depth 1 https://github.com/hlissner/doom-emacs "$emacsdir" - fi - ''; - }; -}

`;; Needed to add javascript-eslint to the the next-checker after lsp so that it would actually load, as that wasn’t happening by deafult ;; also needed to runit after the lsp-afer-initalize-hook because otherwise ‘lsp wasn’t a valid checker (add-hook ‘lsp-after-initialize-hook (lambda () (flycheck-add-next-checker ‘lsp ‘javascript-eslint))) ;; https://github.com/hlissner/doom-emacs/issues/1530 ;; Potential alternative to the above ;; (after! (:and lsp-mode flycheck) ;; (flycheck-add-next-checker ‘lsp ‘javascript-eslint))

The performance lag of Spacemacs was addressed by Doom Emacs ( https://github.com/hlissner/doom-emacs ). Have you tried Doom Emacs by any chance. After syncing everything, the performance is stellar in my opinion.

but I just realized, you're probably better off using doom emacs. The defaults are sane, customizations are almost always optional and the community's really active/helpful. (Disclaimer: I'm a doom emacs user with ~2k lines of config)

While Doom is more opinionated, it's not too difficult make Emacs your own, most of the choices are optimized anyway. Currently the head of Spacemacs devs is not active on the project anymore. Also I don't think it's hard to upstream code to Doom, as long as the code is thoroughly written, take a similar example on both sides: the introduction of a completion engine as layer/module (same packages are installed): - https://github.com/syl20bnr/spacemacs/pull/14901: 23 comments, 7 participants - https://github.com/hlissner/doom-emacs/pull/4664: 576 comments, 20 participants

Also Doom emacs has one. https://github.com/hlissner/doom-emacs https://github.com/hlissner/doom-emacs/tree/master/modules/lang/common-lisp

Nowadays, I use https://github.com/hlissner/doom-emacs with WSL2 but only for org-mode. For code, I have either Sublime Text or VS Code.

Then the slowness that you're seeing is probably Windows-specific, and that's why everyone else is telling you that Magit is actually fast.

WSL might make things faster.[1] IIUC, the problem is that starting new processes is much slower on Windows than on Linux/Unix and Magit relies heavily on that. This seems to have plagued Git tooling more generally but maybe this got fixed since then.[2]

[1] https://emacs.stackexchange.com/a/58444

[2] https://github.com/magit/magit/issues/2395#issuecomment-1710...

You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day when you're feeling adventurous. You'll ultimately become far more powerful than you've ever been. Especially if you delve into elisp over time. I use Spacemacs, which is bloated and has bugs, but it has so many features that I haven't undertaken the massive endeavor to replace it from scratch yet.

> Even in this article just a few sentences after stating we should start from first principles he then jumps into the assumption of the "desktop".

Agree. Although I can see how the idea of "first principles" can be a very difficult starting point. A blank sheet of paper is a scary monster.

There's a huge breadth and depth of non-"desktop" GUIs out there, some (like smartphones) are even wildly successful. It's good to explore them for inspiration. Some of my favourites:

- Arcan (https://arcan-fe.com/about/) - I won't attempt to summarize, just dive in!

- SailfishOS (https://sailfishos.org/) - mobile UI focused on interaction through gestures / swipes; I've used it as my daily driver for a couple years.

- Speaking of mobiles, classic Nokia UIs allowed you to navigate to a specific item in the menu by pressing the corresponding digit on the dial pad. Once you learned where a particular item is, accessing e.g. your SMS inbox was extremely quick.

- Apple Watch / WatchOS (https://www.apple.com/watchos/) - I've always loved the idea of a device where one of the primary interaction methods was a wheel/dial of some sort. The watch even gives you context-sensitive tactile feedback.

- ZUIs in general (https://en.wikipedia.org/wiki/Zooming_user_interface) and the work of Jef Raskin in particular: https://en.wikipedia.org/wiki/Archy_(software) - this is the guy who helped design the Macintosh, but his other work took a radically different route.

- Magit (https://magit.vc/). Many common git operations are reduced to a couple of keystrokes; the obscure features are more discoverable, and the cumbersome procedures (such as rebasing, or staging individual hunks) become simple and intuitive. Also check out transient (https://github.com/magit/transient), which is the "UI toolkit" that powers Magit.

This can be done most comfortably with org-mode in emacs. It offers a lot of features, and they all operate on plain text. There are also nice integrations for git and languagetool, but I guess those are less exclusive.

How does this differ from https://magit.vc/ ?

I would rather see innovative tools that lessen our dependency on 50+ year old tech. This is still a glorified teletype. It uses AI to autosuggest git commands? Contrast with Magit[1], which (while it has a tiny bit of a learning curve, but also nowhere near 23M in funding) actually makes interacting with git a pleasure.

[1]: https://magit.vc

Also was using Emacs (org-mode)[https://orgmode.org] for years with (Magit)[https://magit.vc] package for git. I feel org-mod is a precursor to Roam Research, Obsidian, et al. Hit the spot for years but I wanted editing on mobile so that’s why I’m here. :)