Executing CtrlPSwoop increase CPU utilization to 100%
Nobody has claimed this yet.
- Dominant language
- Vim Script
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
When I run : CtrlPSwoop CPU utilization is increased to 100%.
Does CtrlPSwoop search for other files or only current buffer? AFAIK helm-swoop search only in the buffer.
Is there any option to limit the search to current buffer?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the :CtrlPSwoop command and inspect the CtrlPSwoop implementation to determine whether it searches beyond the current buffer. Trace the cause of the reported 100% CPU utilization and verify whether a current-buffer-only limit is possible. Done means the command no longer causes the reported CPU spike and its search scope is documented or configurable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vim
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100