.emacs.d VS helm

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.

(setq inhibit-startup-message t) (setq visible-bell t) (setq make-backup-files nil) ; Disable the creation of ~ files (setq auto-save-default nil) ;; stop creating those #auto-save# files (setq display-line-numbers-mode t) ;(scroll-bar-mode -1) ; Disable visible scrollbar. Only for visual GUI ;(tool-bar-mode -1) ; Disable the toolbar. Only for visual GUI ;(tooltip-mode -1) ; Disable tooltips (menu-bar-mode -1) ; Disable the menu bar. Only for visual GUI ;(set-fringe-mode 10) ;(setq visible-bell t) ; Mac OSX specific ;mac-function-modifier ;mac-control-modifier) ;mac-command-modifier ;mac-option-modifier ;mac-right-command-modifier ;mac-right-control-modifier ;mac-right-option-modifier ;; key bindings (when (eq system-type 'darwin) ;; mac specific settings (set-terminal-coding-system 'utf-8) (set-keyboard-coding-system 'utf-8) (prefer-coding-system 'utf-8) (setq mac-command-modifier 'meta) (setq mac-control-modifier 'control) (global-set-key [kp-delete] 'delete-char) ;; sets fn-delete to be right-delete ) ;; ORG Mode (global-set-key (kbd "C-c l") #'org-store-link) (global-set-key (kbd "C-c a") #'org-agenda) (global-set-key (kbd "C-c c") #'org-capture) ;; packages (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/")) ;; Comment/uncomment this line to enable MELPA Stable if desired. See `package-archive-priorities` ;; and `package-pinned-packages`. Most users will not need or want to do this. ;;(add-to-list 'package-archives '("melpa-stable" . "https://stable.melpa.org/packages/") t) (package-initialize) ;; LSP-mode config (setq package-selected-packages '(lsp-mode yasnippet lsp-treemacs helm-lsp projectile hydra flycheck company avy which-key helm-xref dap-mode)) (when (cl-find-if-not #'package-installed-p package-selected-packages) (package-refresh-contents) (mapc #'package-install package-selected-packages)) ;; sample `helm' configuration use https://github.com/emacs-helm/helm/ for details (helm-mode) (require 'helm-xref) (define-key global-map [remap find-file] #'helm-find-files) (define-key global-map [remap execute-extended-command] #'helm-M-x) (define-key global-map [remap switch-to-buffer] #'helm-mini) (which-key-mode) (add-hook 'c-mode-hook 'lsp) (add-hook 'c++-mode-hook 'lsp) (lsp-treemacs-sync-mode 1) (setq gc-cons-threshold (* 100 1024 1024) read-process-output-max (* 1024 1024) treemacs-space-between-root-nodes nil company-idle-delay 0.0 company-minimum-prefix-length 1 lsp-idle-delay 0.1) ;; clangd is fast (with-eval-after-load 'lsp-mode (add-hook 'lsp-mode-hook #'lsp-enable-which-key-integration) (require 'dap-cpptools) (yas-global-mode)) ;; theme (load-theme 'modus-vivendi t)

Oh wow wow wow! I just checked your commit on the repository. That's so amazing. I really appreciate that. And I also found a convenient donation link.

Next you "only" have to remember (elisp) function names. "Completion UIs" like ivy/counsel, icomplete, helm or vertico/consult, give you a nice auto completion list on M-x (choose the one of them, you like the most). Some of those Completion UIs will display existing keybindings and a short documentation for commands, near the auto complete candidates. So you will start to remember more keybindings without "learning sessions", just because invoking functions via keybindings is much faster (more convenient).

I use imenu, and helm-imenu to filter out the list interactively. Instead of scrolling through, you "jump" to an item via completion like helm-imenu, which filters all headings interactively in real-time as you type.

I personally use Helm, so I can manage all files (open, delete, copy, rename, etc) all from completing prompt directly, I don't need to open Dired for that.

Helm 1.2 release was in September 2011: https://github.com/emacs-helm/helm/releases/tag/v1.2

I updated helm recently and when trying to use it after startup I was hitting "Defining as dynamic an already lexical var" . debugger showed me it was due to `ffap-machine-p-local` not being defined yet, digging into helm-lib.el i found that it is due to the ffap let bindings added recently to `helm-guess-filename-at-point` - the first one was to address this issue https://github.com/emacs-helm/helm/issues/2574 and more recently two more ffaps were let bound. I can fix by adding `(require 'ffap)` in the helm `use-package` `:config` -- wondering if this is the recommended way or if it might be something worth living inside helm-lib.el near the top where it requires cl-lib already?

Related to https://github.com/emacs-helm/helm/discussions/2577

Yes, Helm. Probably others like Embark.