-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Completion in minibuffer: Making inhibit-read-only local to *helm-mode-completion-at-point* while let-bound! #4224
Comments
It would help us to help you if you can provide some more details :-) Have a look here. |
I believe this happens when you try to do tab completion while helm is loading which happens on about a 1 second delay |
It's not while it's loading, I can wait on the home screen forever and it will still happen, however, it appears to only happen the first time. Is there a way do non-helm-completion in the minibuffer? if I type |
To clarify, I believe the problem occurs if you execute a command that On Fri, Dec 18, 2015 at 4:35 PM Adam Olsen notifications@github.com wrote:
|
I can wait as long as I want. It will still happen. But only the first time. |
Here's a more direct test. Comment out this line, restart and see if you can reproduce it |
@justbur I think your link is (already) outdated. You should link to a specific commit version (pressing |
Actually I can reproduce this even if helm is not deferred, so I was wrong about that |
I was seeing this issue this morning, then Spacemacs seemed to update to v.0.105.21 and now the issue seems to have gone away. |
@synic did you figure out a workaround for this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
I often open up spacemacs and type
:e ~/Pro[tab]
to open a file. Tab completion is hard to see because that message pops up, obscuring the completion.How can I make that stop?
System Info
The text was updated successfully, but these errors were encountered: