.emacs.d VS doom-emacs

In my Helm, I have to actively choose the candidate to confirm it. So I can type in both paths that are shorter or longer then existing ones. I even made a video to demonstrate it, the thread was relatively recently up I think. My Helm setup is here it if helps you, find Helm in the list of packages.

I also use Helm, and I have no problems. Just keep typing, once you typed a letter that does not exist in a path name it will stop completing. I don't know if I have some special option enabled/disabled; I don't think you need it, but you can see my Helm config (just scroll down untill you find "Helm").

When all deps are installed,my config is over 200 packages. On my Arch Linux desktop I built in 2016, with i7 4.6k (haswell) it starts ~0.7 secs, but init time will be anything between 0.5 ~ 0.8 secs, i guess depending on what system does. So all things same, init time will vary.

I am using it in my literate org-config. If you scroll down, there is a big list of packages, and I have done a small wrapper around helm-imenu, to jump to a package configuration. Looks like this.

That does not work for completions, at least not for me. It works for keymaps, so you can have mode specific (or really any) keymap in src blocks. I have been using his method myself in my init file generator for quite a while now. If you (or anyone) knows/have an idea how to expand it for completions and eldoc, I would be really happy to hear.

I don't know what if it is more robust but I use more or less plain dired with just some options turned on to make it less noisy to look at, but I don't "manage" my files so much to be honest. I do use some extras from dired-hacks, and my own dired-auto-readme, but that is about it. You can check my setup if you wish, look at "dired" under packages and in Lisp folder for "dired-extras.el".

I personally put all custom lisp in a special directory and scrape autoloads myself. If you are curious, you can check under "generator", functions generate-autoloads and collect-autoloads, but there is nothing special, just plain text search and copy-paste programmatically. I don't recommend to use it though.

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