fix(action): grep_string select_default with nil column #2447
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Regression bug from #2416 where
grep_string
results without column numbers where not respecting the row number onselect_default
when usinggrep_string
with the command:Telescope grep_string search=<CR>
Closes #2444
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list relevant details about your configuration
:Telescope grep_string search=<CR>
to grep for anything that's not that on the first line of the fileselect_default
on some entry - the file should open on the correct line:Telescop grep_string<CR>
works as expected taking you to the correct row/col of the file:vnew
:Telescope buffers
and open the buffer from above -> cursor should be in the same location between the two windows:vnew
:Telescope find_files
and open the file from above -> cursor should be in the same location between the windows (previously would always go to [1,1])Configuration:
NVIM v0.9.0-dev-1290+g2257ade3d
Linux archlinux 6.1.12-arch1-1
Checklist: