Search editor go to location improvements#135227
Search editor go to location improvements#135227JacksonKearl merged 3 commits intomicrosoft:mainfrom
Conversation
- Added option to go to and select the match - Fixed cursor placement with initial whitespace
|
Thanks for creating this! Could you please split out the selection patch so that this PR impacts only search editor code? |
|
@JacksonKearl, thanks for looking. Which part do you want me to split out? I assume you mean to only keep the code to fix one of the two issues in this branch, but I'm not sure which one you want kept in here and which to open a new PR for. |
|
Thanks, @JacksonKearl! I update it. A far as I can tell, I cannot accomplish #128927 with an extension. If I create a new pull request for that, do you think it could be merged? |
|
|
||
| const FILE_LINE_REGEX = /^(\S.*):$/; | ||
| const RESULT_LINE_REGEX = /^(\s+)(\d+)(:| )(\s+)(.*)$/; | ||
| const RESULT_LINE_REGEX = /^(\s+)(\d+)(: | )(\s*)(.*)$/; |
There was a problem hiding this comment.
The separator should always be length two, yes? So two spaces on the alternate side:
/^(\s+)(\d+)(: | )(\s*)(.*)$/;|
Pushed a change to fix an off-by-one on context lines, besides that looks good. Thanks for this! |
|
As for #128927, IMO handling untyped args in the |
|
Thanks. I was thinking if I could get decorations (#48364) I could write an extension to do this instead, but that's not supported. What if I implement it without the args? I haven't checked yet, but I'm wondering if after calling |
|
If you can implement it with changes localized to search editor files I would consider it. |
|
Great. Thank you, @JacksonKearl. I found a way to do that in #136002. |
This PR fixes #135226.