.emacs.d VS doom-emacs

If you want to dip your toes, I'd maybe try out https://github.com/doomemacs/doomemacs if you like vi style keybindings or https://github.com/seagle0128/.emacs.d or if you want to use something more traditional. Then I'd recommend https://github.com/gcv/julia-snail for the julia side of things.

Do not use doom as the heretics suggest! It is an awful experience and very janky, they also change how emacs is configured in a weird way that doesn't lead to one understanding the lisp or how emacs starts up. I'd suggest witchmacs (https://github.com/snackon/Witchmacs) or centaur emacs (https://github.com/seagle0128/.emacs.d) to get a feel of how a config actually looks like. With doom it is obscured under so much. As an exvimmer I moved to god-mode and emacs bindings just because everything always works with these. Using evil gets a little complicated since it doesn't always function properly. But using evil is probably best for you at the moment.

My favourite emacs starter kit is centaur emacs, it makes great use of hydras and improves on the standard key bindings. But I have to say I love the look of NΛNO and the svg-lib. u/Nicolas-Rougier, have you thought about combining some of the features of centaur with your work?

If you are looking for an alternative to doom without evil mode, I recommend centaur emacs. https://github.com/seagle0128/.emacs.d

To me, Vanilla Emacs config certainly. I create Centaur Emacs for myself and share to others.

There is https://github.com/seagle0128/.emacs.d and there is my own distro https://github.com/Ultra-Hax/magmamacs which is more minimal but less customizable and more opinionated both of these distros are very minimal and blazing fast.

Example configuration - https://github.com/seagle0128/.emacs.d/blob/e225dbe431f1e7ad368f3fe11d63ceb60c5acfcb/lisp/init-window.el#L142

$ 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.