Replies: 1 comment
|
This is intentional, since otherwise the preview buffer would too often switch back to the original buffer, which would lead to a lot of flicker. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi ,
I have a question regarding the preview behavior in
consult-bufferwhen mixing sources with different preview configurations.Context
I use
consult-bufferwhich aggregates multiple sources (buffers, recent files, etc.).My configuration is as follows:
consult-customizewith a specific:preview-key, so they do not auto-preview).The Issue
I encountered a scenario where the preview window does not clear when the selection moves from a previewable candidate to a non-previewable one.
Reproduction Steps:
"aaa"."aaab".M-x consult-buffer."aaa":"aaa"(buffer) is selected."aaa"is previewed correctly."b"so the input becomes"aaab":"aaab"(recent file)."aaab"."aaa".Expected Behavior
When the selection switches to a candidate that does not trigger a preview (either because auto-preview is off for that source or the specific
:preview-keyhasn't been pressed), I expected the preview window to be cleared (restored to the original state).Currently, seeing the stale preview of
"aaa"while"aaab"is selected feels misleading, as it suggests"aaa"is still the active context.Question
consultsuch that selecting a non-previewable candidate automatically clears any existing preview?All reactions