-
Notifications
You must be signed in to change notification settings - Fork 29
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
Displaying the completion list should not reset position in the *goals* buffer #8
Comments
This seems to be tied to displaying types in the minibuffer; it shows up for completing theorems (which displays their type in the minibuffer), but not for completing, e.g., |
I think your analysis is right. The problem is probably due to coq-PG reprinting the goal when a new command is issued. I may be able to do something on the company-coq side, but it's really a PG issue. |
Could you try this fix when it lands into MELPA? It should fix this bug. |
Thanks! Can you ping me when it lands in MELPA? |
Sure |
Note to self. The fix for this should really be merged into PG; atm company-coq saves the buffer position before calling the prover, and resets the position after calling it, causing disagreeable jitter. |
Should be in MELPA now :) |
I have this problem too. |
Hi @lczch . Can you give me a bit more details? This problem should have been fixed a while back. |
See cpitclaudel/company-coq#8 and cpitclaudel/company-coq#32 for some background info.
See cpitclaudel/company-coq#8 and cpitclaudel/company-coq#32 for some background info.
Pushed a cleaner fix to a branch of PG at https://github.com/ProofGeneral/PG/tree/fix-scrolling-buffers. |
When I have a large goal, and I am scrolled to a particular point in the
*goals*
buffer, if I type something, and the completion drop-down shows up, the*goals*
buffer resets to its default scroll point, much the same way that it does when I executeShow.
orC-c C-p
. This is annoying, as it means I can't refer to a particular point in the goal while typing things.The text was updated successfully, but these errors were encountered: