Timeline for Grep on type with delay. Scripting / Looking for plugin
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 14, 2019 at 17:55 | vote | accept | droso | ||
| Jan 14, 2019 at 16:23 | answer | added | Hotschke | timeline score: 0 | |
| Jan 13, 2019 at 14:53 | comment | added | Hotschke |
I think I understand you now better. See here github.com/junegunn/fzf.vim/issues/714#issuecomment-428802659 and for :Ag here github.com/junegunn/fzf.vim/issues/346
|
|
| Jan 12, 2019 at 17:17 | comment | added | droso | What fzf.vim does is execute "grep" once (join all files) and then fuzzy search this one big buffer (this results in: 'test' will find all the occurance of 'test' in all files but also will show all the lines from the file that have 'test' in its name (e.g. test.txt) (because grep adds name of the file at the beginning of the line)). | |
| Jan 12, 2019 at 7:01 | comment | added | Hotschke |
FZF runs asynchronously which means it will not block you. I do not know an option which sets a timedelay to wait after each keypress until fzf starts. I think this would contradict the mission of fzf being Blazingly fast. What is your actual problem with the current situation? Are you afraid that fzf when often used will use too much CPU which will extend running time of long-running tasks, shorten battery life, ...?
|
|
| Jan 11, 2019 at 21:38 | comment | added | Ralf |
Sorry, but I don't understand what you want. From the word "grep" I would recommend to read :help :vimgrep and :help :grep.
|
|
| Jan 11, 2019 at 17:55 | review | Close votes | |||
| Jan 16, 2019 at 18:13 | |||||
| Jan 11, 2019 at 16:20 | review | First posts | |||
| Jan 11, 2019 at 21:48 | |||||
| Jan 11, 2019 at 16:19 | history | asked | droso | CC BY-SA 4.0 |