Provides an extra CAPF for completing Yasnippet keys, automatically triggering expansion on select. Further, the user can fill in the template as they do normally.
Currently, this is left as a job for the user, as the package has not yet been
submitted to any archives. Thus, installing entails placing this repo somewhere
in load-path and possibly compiling it to byte- and/or native-code. If you use
a package manager, check their documentation on how to use packages stored in
git repositories.
Add yasnippet-capf to completion-at-point-functions, with code such as the
following in your config:
;; "Global" setup; enabled anywhere Yasnippet is active.
(add-hook 'yas-minor-mode-hook
(lambda () (add-to-list 'completion-at-point-functions #'yasnippet-capf)))
;; OR
;; Per-mode setup; enabled only for the modes you select. Note Yasnippet
;; should also be separately activated in these.
(add-hook 'some-mode-hook
(lambda () (add-to-list 'completion-at-point-functions #'yasnippet-capf))If you use other CAPFs as well (very likely), beware that order matters. They
are tried in order, and unless configured otherwise, only the completions from
the first function to return non-nil will appear. A simple solution is to adjust
the :depth argument passed to add-hook, to change the order to your liking.
This CAPF is configured to allow other CAPFs to run after it, so it should be
to add it early in the sequence.
In the most general sense, just use completion regularly, it’ll have snippet candidates now. What this looks like depends highly on your completion frontend, be it the in-built Emacs feature, corfu, company etc. Additional elements may appear depending on what your setup supports, such as a preview of the expansion as documentation, icons and annotations.
See the LICENSE file next to this README.