M
@tchauhan @jameshowell @oantolin You could try Drepl for a Python REPL with better completion. I have not used it so far, so I don't know how well it works in practice.
REPL protocol for the dumb terminal. Contribute to astoff/drepl development by creating an account on GitHub.
GitHub (github.com)
@tchauhan cape-dabbrev is similar to dabbrev-capf, but a little more polished. dabbrev-capf had bugs in the past, but I think they are fixed at least in Emacs 31. Regarding Python REPL completion I cannot help. All I know is that the Capf is broken. @jameshowell @oantolin
@oantolin I use consult-history for both (repl and minibuffer), but mainly because I've bound it to the more convenient key (M-r).
@tchauhan @jameshowell
@tchauhan Another example is `cape-history` vs `consult-history`, which you can use in Comint, Shell or Eshell buffers. `cape-history` displays the candidates via in-buffer completion (e.g. Corfu) while `consult-history` displays the candidates via `completing-read` (e.g. Vertico).
@jameshowell @oantolin
@jameshowell Embark is easy to get started with. For example move point to a symbol and run `M-x embark-act`. It should display the available actions. If you want to invoke the standard action, e.g., jump to symbol, invoke `M-x embark-dwim` on a symbol to point. Of course Embark recognizes many more object types at point than symbols. This means we get lots of context dependent commands.
@oantolin
@tchauhan What do you find difficult about Cape?
Cape basically provides a bunch of completion backends, so called Capfs. You can either add the Capfs to the `completion-at-point-functions` list, or invoke them directly, for instance `M-x cape-emoji` or `M-x cape-file`.
Another way to think of it - Cape is to Corfu what Consult is to Vertico.
@jameshowell I definitely recommend to add Embark to the mix. Embark is like a left click or right click menu for objects at point (or in the completion minibuffer), but keyboard driven. @oantolin
