mirror of
https://github.com/joaotavora/yasnippet.git
synced 2025-10-13 05:03:04 +00:00
* doc/faq.org: Note that Flyspell problem is (now fixed) Emacs bug.
This commit is contained in:
parent
9cedd596ec
commit
189f7375b6
14
doc/faq.org
14
doc/faq.org
@ -30,23 +30,17 @@ final newline automatically.
|
||||
|
||||
* Why doesn't TAB navigation work with flyspell
|
||||
|
||||
A workaround is to inhibit flyspell overlays while the snippet is
|
||||
active:
|
||||
This is Emacs Bug#26672, so you should upgrade to version 25.3 or
|
||||
better. Otherwise, a workaround is to inhibit flyspell overlays while
|
||||
the snippet is active:
|
||||
|
||||
#+BEGIN_SRC emacs-lisp
|
||||
(add-hook 'flyspell-incorrect-hook
|
||||
#'(lambda (dummy1 dummy2 dymmy3)
|
||||
#'(lambda (&rest _)
|
||||
(and yas-active-field-overlay
|
||||
(overlay-buffer yas-active-field-overlay))))
|
||||
#+END_SRC
|
||||
|
||||
This is apparently related to overlay priorities. For some reason, the
|
||||
=keymap= property of flyspell's overlays always takes priority over the
|
||||
same property in YASnippet's overlays, even if one sets the latter's
|
||||
=priority= property to something big. If you know emacs-lisp
|
||||
and can solve this problem, send a message to bug-gnu-emacs@gnus.org
|
||||
or the [[Github issue tracker][https://github.com/joaotavora/yasnippet/issues/]].
|
||||
|
||||
* How do I use alternative keys, i.e. not TAB?
|
||||
|
||||
Edit the keymaps [[sym:yas-minor-mode-map][=yas-minor-mode-map=]] and [[sym:yas-keymap][=yas-keymap=]] as you would
|
||||
|
Loading…
x
Reference in New Issue
Block a user