Fix vim replace not escaping $ - #53277
Conversation
11b9e1a to
bdb9eaa
Compare
bdb9eaa to
71924a3
Compare
$
|
This passed my initial desk-check, but after sitting down to make some improvements it no longer seems to be behaving. I pulled down the latest from main, but I couldn't say for sure that that's what broke it. Marking as draft until I can make it work again. EDIT: Re-opening because it turn out I was test from the Zed I was writing Zed in (preview), not the Zed I was writing. Oops! Fix still works as intended. I looked into making the text populated by the search bar a little more aesthetic, but the existing Altogether, since the replacement bar is not highlighted at all in today's Zed, I leave the design choice of how/if to do that for another commit, modulo other opinions. |
|
Thanks for this! |
|
@zed-zippy approved |
Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes #zed-industries#42292 The text inserted in the search ('\$SEARCH') and replace ('$$OTHER') inputs of the top-panel is a little anti-aesthetic, but that seems out of scope for this issue. Release Notes: - '$' in the second clause of vim-style '%s/find/replace/g' actions is correctly escaped. Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com>
Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes #zed-industries#42292 The text inserted in the search ('\$SEARCH') and replace ('$$OTHER') inputs of the top-panel is a little anti-aesthetic, but that seems out of scope for this issue. Release Notes: - '$' in the second clause of vim-style '%s/find/replace/g' actions is correctly escaped. Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com>
Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes #zed-industries#42292 The text inserted in the search ('\$SEARCH') and replace ('$$OTHER') inputs of the top-panel is a little anti-aesthetic, but that seems out of scope for this issue. Release Notes: - '$' in the second clause of vim-style '%s/find/replace/g' actions is correctly escaped. Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com>
Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes #zed-industries#42292 The text inserted in the search ('\$SEARCH') and replace ('$$OTHER') inputs of the top-panel is a little anti-aesthetic, but that seems out of scope for this issue. Release Notes: - '$' in the second clause of vim-style '%s/find/replace/g' actions is correctly escaped. Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com>
Self-Review Checklist:
Closes ##42292
The text inserted in the search ('$SEARCH') and replace ('$$OTHER') inputs of the top-panel is a little anti-aesthetic, but that seems out of scope for this issue.
Release Notes: