![]() :-) Do you see the same issue with plain grep? That will go a long way toward understanding whether the problem is with the tool or your environment. With all that said, you didn't actually answer my question. It wouldn't surprise me at all that your command is running slowly because of something of that nature. I am not someone with a lot of Windows knowledge, and my experience in that ecosystem is that 1) I/O on Windows is much slower than similar operations on Linux and, perhaps most significantly, 2) Windows often has virus/malware/whatever scanners running that severely cripple I/O throughput. From ripgrep's perspective, it's just printing to a generic file handle, whether that's a console or a file or another process's stdin, ripgrep generally doesn't care. Do you have an SSD? Otherwise, the output redirection isn't really something that ripgrep cares about. My best guess is that your problem is Windows and/or a slow hard drive. I have updated to the latest 11.0.2 version and the problem has persisted.Output redirection still took a lot of time. I used the flags -vimgrep, -no-line-buffered, -no-block-buffered in the folder where the problem was occurring and the problem persisted.I would have assumed providing the glob pattern would make both cases the same but the miscellaneous video, audio and other text files seem to be causing the delay in output redirection. In this new folder, output redirection is instantaneous. The new folder was 900 KB big with 2,200 text files. I created an empty test folder, and copied all the files that match the glob, i.e., all the files matching *.ascii.txt. Running the output redirection command in this folder was where the problem was occurring. My production folder is 6.4 GB with lots of generated videos and audio files.After running the output redirection command once fully and waiting for a long time, subsequent output redirections are instantaneous.The command is very slow and takes a lot of time. However, if I try to redirect the output rg -g *.ascii.txt money > ripgrep_output.txt ![]() If I run the command: rg -g *.ascii.txt money Output redirection is very slow in ripgrep when there are lots of miscellaneous files. I would be grateful if somebody could help me out in debugging this issue. Searching the open issues on the vim Github repository.Running gvim -u NONE -U NONE and the problem was still present.When I run the same command on the command-line, it takes around 20 seconds for the first run, then is instantaneous for subsequent queries as the data has been loaded into memory. It gets stuck on !rg -vimgrep -g *.ascii.txt money >C:\users\me\AppData\Local\Temp\VIe1F82.tmp Searching through a lot of text files takes too long (hundreds of seconds) and sometimes the search doesn't even complete. When I set the grepprg with the following command: set grepprg=rg\ -vimgrep And please those of you who deign to grace us with your vim wisdom - be kind. Vim Awesome: list of popular vim plugins.ĭon't be afraid to ask questions, this sub is here for the vim community.Learn Vimscript the Hard Way: is a book for users of the Vim editor who want to learn how to customize Vim. ![]() Derek Wyatt's Vim tutorial videos: video tutorials by Derek Wyatt's.Vimcasts: screencasts by the author of practical vim.7 habits of effective text editing: a short guide on getting better at editing by the Vim author.usevim: a vim blog with some great outbound links.Patrick Schanen's Vim Page: an index of vim resources more complete than this list.vi.: questions and answers stackexchange style.: the most popular vim wiki, lots of great content. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |