counsel-describe-function and `...' quoted stuff #126
Comments
I don't have this problem - it works as expected for me. Can you reproduce with emacs -Q? Note that the function at point must be interned - that threw me off when I tested just now with emacs -Q. After interning the function, it worked fine. |
I just found out it is mode-specific (most probably syntax-table specific). With emacs -Q in an elisp-mode buffer, it works as expected. |
Thanks. |
After abo-abo#126 has been solved, the regexp has been changed to "\\`[`']?\\(.*\\)'?\\'" where the trailing ' is optional ("'?"). However, the preceeding "\\(.*\\)" group will already capture the trailing ' because .* is greedy. Now I've replaced it with the non-greedy .*? which makes it work again.
I use
counsel-describe-function
andcounsel-describe-variable
as drop-in replacements for the standard commands. However, there's one thing where the standard ones work better.When point is somewhere in ``some-command-name'
and you do
C-h f`, then `some-command-name` is used as default value. With the counsel variants, the quoting with ` and ' prevents that (actually, it's the trailing single quote which is the problem).The text was updated successfully, but these errors were encountered: