When doing case conversions, specifically in the case of an empty selection, in both VS Code and Sublime, the cursor winds up being in a different place relative to where it started. In VS Code, the cursor maintains it position in the text, no matter if the text expands or shrinks https://github.com/zed-industries/zed/assets/19867440/b24f5d86-c315-4a72-9ed4-3732b490ea9a In Sublime, I have no idea what is going on: https://github.com/zed-industries/zed/assets/19867440/05f21303-6e42-47b2-b844-7accd0bf05d7 I thought it would be a better experience if, when doing an empty selection transformation, we simply expand the selection and park the cursor at the end of the newly-transformed text. https://github.com/zed-industries/zed/assets/19867440/833619ef-04e2-47b6-ad4e-e2b43d54fb2b This feels similar to us expanding the selection when doing line manipulations: https://github.com/zed-industries/zed/assets/19867440/c30c5332-787d-4cf0-a9ee-e66c3c159956 Selections are adjusted to match however each word expands and shrinks, even when there are multiple: https://github.com/zed-industries/zed/assets/19867440/d7073aac-8a59-4f2c-b0e5-1df37be1694c Release Notes: - Improved behavior of empty-selection case transformations by selecting resulting word. - Fixed some bugs with overflow
2 files changedLine totals unavailable