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
I am trying to replace my fine-tuned ido (+ addons) setup with ivy, and in most respects, it's a step forward! One issue I have is this, however: I would like to use ivy-completing-read as a drop-in replacement for as many things as possible, but I still want to set the completion style as per ivy-re-builders-alist for some of these commands.
Are there any downsides to passing :caller this-command where ivy-completing-read calls ivy-read?
This is what I've done to get non-flx completion for org-refile (while I use flx completion everywhere else), and so far that works fine.
The text was updated successfully, but these errors were encountered:
Are there any downsides to passing :caller this-command where ivy-completing-read calls ivy-read?
The downside is that it's impossible to tell whether the :caller was explicit of passed via ivy-completing-read. Removes granularity. Also, this-command can be manipulated. Still, I put this-command on priority list of keys behind :caller. So your case should work fine now.
I am trying to replace my fine-tuned ido (+ addons) setup with ivy, and in most respects, it's a step forward! One issue I have is this, however: I would like to use
ivy-completing-read
as a drop-in replacement for as many things as possible, but I still want to set the completion style as perivy-re-builders-alist
for some of these commands.Are there any downsides to passing
:caller this-command
whereivy-completing-read
callsivy-read
?This is what I've done to get non-flx completion for
org-refile
(while I use flx completion everywhere else), and so far that works fine.The text was updated successfully, but these errors were encountered: