-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem when setting avy-all-windows
to t
with same buffer displayed in multiple windows
#47
Comments
Can't reproduce, works fine for me. |
OK, I will then need to understand how one of the avy goto functions works and see what happens differently if the same buffer is shown in both windows vs different buffers in the windows. I can consistently recreate this problem by taking any buffer and then,
The problem does not show up when doing Also if this helps, this is the only customization I do for (setq avy-style 'at-full)
(setq avy-styles-alist '((avy-goto-word-1 . pre))) |
Actually, the problem happens when I set the avy style to (setq avy-style 'pre) Summary: Problem with any avy command when the same buffer is shown in multiple windows and |
OK, I see it now. |
* avy.el (avy--overlay-at-full): Update. Re #47
This change alleviates the problem slightly. I don't understand why this is happening, could be an Emacs bug. |
I see that the problem starts happening at the point where we run out of jump shortcuts (avy keys). For example, by default we have 9 keys in Example: (setq avy-keys-alist '((avy-goto-line . (?a ?s ?d ?f ?g ?h ?j ?k ?l ?b ?n ?m)))) But the problem returned once I had 4 windows in the frame and there were more lines to index than the number N^2-N |
Also, from the line where this problem starts occurring, the line contents are shifted to the right even when the style for |
I get the below on calling
avy-goto-line
withavy-all-windows
set tot
.Here I have both windows showing the same buffer. This problem does not happen if the windows are showing different buffers.
You can click on the below image to see it enlarged.
The text was updated successfully, but these errors were encountered: