You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even with my fix from the second commit in #3, avy-goto-subword-0 isn't too accurate. With a word like ThisIsATest, it considers This, Is, and ATest as subwords. But of course ATest are actually two subwords.
I think a proper fix would be to re-use subword-forward-regexp defined in emacs' subword.el. (That also requires case-fold-seach to be nil, so my second commit from #3 is correct anyway.)
The text was updated successfully, but these errors were encountered:
Not sure. If subword-mode is active, then the user has obviously a preference for subword navigation. OTOH, subword gives many more candidates in e.g. Java buffers and other langs using CamelCaseStyle, and usually you want to jump to the beginning of a method, class, field, or variable in at least 90% of all cases. So I think I prefer the current behavior.
By the way: I noticed that with avy-goto-subword-0, the paths are printed before the leading char of the subword. With avy-goto-word-0 (and I think with all other avy-jump commands) they are printed after the leading char. Ah, you've actually explained that in #5, i.e., subword uses avy--overlay-pre, the others avy--overlay-post. :-)
Even with my fix from the second commit in #3,
avy-goto-subword-0
isn't too accurate. With a word likeThisIsATest
, it considersThis
,Is
, andATest
as subwords. But of courseATest
are actually two subwords.I think a proper fix would be to re-use
subword-forward-regexp
defined in emacs'subword.el
. (That also requirescase-fold-seach
to be nil, so my second commit from #3 is correct anyway.)The text was updated successfully, but these errors were encountered: