Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Vim sometimes freezes when I select a file
See original GitHub issueProblems summary
Vim occasionally freezes when I select a file.
Expected
The file should open, vim should not freeze.
Environment Information
-
fzf-preview version (package.json):
0.4.9 -
OS: MacOS
-
Vim/Neovim version: Neovim HEAD
Screenshot
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
sometimes my file just freezes in my vi |vim, what happened?
Sometimes when I edit my file using vi or vim, my file just freezes. Even if I type Ctrl+C or Ctrl+D , it...
Read more >How to fix Vim freezes - Programming is Magic
To unfreeze program you must press Ctrl+Q . It still happens from time to time that I press Ctrl+S while using Vim (old...
Read more >Why is vim frozen? - Unix & Linux Stack Exchange
Because the file, I am editing is very large. This may be caused by a typo or by a "normal" search backwards for...
Read more >sometimes my file just freezes in my vi |vim, what happened?
Sometimes when I edit my file using vi or vim, my file just freezes. Even if I type <kbd>Ctrl+C</kbd> or <kbd>Ctrl+D</kbd>, it still...
Read more >Vim 8.1 is freezing / buffering all input while another process is ...
Hi, I've recently switched to Vim and I'm having difficulty getting Vim to play nicely with certain tools that watch files for changes...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Found the issue. This was somehow caused by the quick-scope plugin.
Not sure why exactly, but disabling quick-scope resolved the issue completely.
OK. Thanks.