cape VS helm

Wow, interesting that my response is getting down voted. It seems not enough that I give away my work for free. Nevertheless I appreciate support from the community, as other Emacs package developers. The support is actually helpful. To clarify, publishing my configuration would translate into quite a bit of work, requiring separation of private and public bits.

At least for Elisp source block one can use font locking to create a custom Capf. Add cape-elisp-block from my Cape package to completion-at-point-functions. Even if you don't want to use Cape you could just copy it to your config. It is a short function.

You can use cape-history from my Cape package. This is similar to consult-history only utilizing completion-in-region instead of completing-read.

Haven't tried configuring it accordingly, but here's the docs: https://github.com/minad/cape

corfu is blazingly fast. Orderless is as well. What is not always blazingly fast is your completion providing backend. You didn't mention where your slow completions are coming from. An LSP server? Dabbrev? Maybe a remote machine? Have you combined results from various backends (e.g. using cape?). Some completions backends are unavoidably slow, others are just not well optimized.

The most straight forward solution is probably the package company-math. (that's what I use but with corfu and cape)

Some time I'll add a mixin for Cape which would make the completion stuff really nice.

If you're set on using the completion system (M-TAB) for this, you could install Cape and use the cape-abbrev command to complete your abbrevs.

Oh, of course your efforts are valuable. I didn't mean to sound discouraging in any way. The point made by /u/xenodium is good - if you have a special candidate source with special behavior, it makes sense to provide a separate lightweight Capf. In contrast, using Tempel for this purpose doesn't make much use of the actual template functionality. Tempel is only a good fit for Org blocks if you use it already anyway, as I do. There is also value in having reference Capfs around, which will be helpful when developers create their own new completion functions. This was also the intention when I created my Cape package, which comes with many simple Capfs. It is always interesting to see what other Emacs users come up with. I am thankful for such efforts - it is inspiring!

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