-
Notifications
You must be signed in to change notification settings - Fork 84
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
async chops off first character when editing many files #329
Comments
Thank you for so comprehensive issue along with the root cause you found! I prefer the second approach but as you said it's a fundamental change. |
anhpt379
added a commit
to anhpt379/dotfiles
that referenced
this issue
Nov 30, 2022
It has been fixed in Nealium/ctrlsf.vim@87b1196, but it's not in upstream yet. For now, let's just fallback to `sync` search mode. dyng/ctrlsf.vim#329
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
Saving an edit with async mode sometimes chops of the first character.
Happens when searching entire moderately sized projects and editing many files.
Examples: updating Javascript Versions in HTML files or includes in PHP Files
See the
How to Recreate
sectionThings about your system and environment(请在此填写你的系统信息)
No Logs
How to Recreate:
Search the files in the folder using this:
CTRLSF Test -filetype php
Before continuing, search 5 spaces in the results buffer
Edit using:
%s/Test/test/
+ Save&WriteRe-Search using:
CTRLSF test -filetype php
Before Edit
After Edit
Note: rerunning the Shell Script resets files to the original (Good for debugging!)
Reason:
ctrlsf#db#MaxLnum()
changing mid-search + not updating already rendered matchesx
results, with max length 7, rendering with the default 4 spaces.My Solution:
The text was updated successfully, but these errors were encountered: