-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
wordDelimiters not working inside tmux with [shift]+[left mouse click] #9382
Comments
@DHowett - I will try to take a look in the next few days. |
So the problem is following: currently shift+click selects a single cell. When the second tap occurs, instead of applying the double-click logic we simply extend the selection, resulting in partial selection. To address this I suggest to extend selection only with shift+single-click. I will issue a PR with more details. |
## PR Checklist * [x] Closes #9382 * [x] CLA signed. * [ ] Tests added/passed * [ ] Documentation updated. * [ ] Schema updated. * [ ] I've discussed this with core contributors already. ## Detailed Description of the Pull Request / Additional comments The selection with shift is quite broken in 1.6. It started with #8611 that introduces cell selection on `shift+click`. This change resulted in the following defect: `shift+double-click`, `shift+triple-click` select only parts of the word. The reason for this is that the first `shift+click` establishes the selection, while the consequent clicks simply extend it to the relevant boundary (aka word / line boundary) However, the logic was broken even before #8611. For instance, `shift+triple-click` had exactly the same handicap: `shift+double-click` was establishing the selection and the third click was simply extending it to the line boundary. This PR addresses the both defects in the following manner: upon multi-click that starts new selection we establish a new selection on every consequent click using appropriate mode (cell/word/line) rather than trying to extend one. For this purpose we remember the position that started the selection.
## PR Checklist * [x] Closes #9382 * [x] CLA signed. * [ ] Tests added/passed * [ ] Documentation updated. * [ ] Schema updated. * [ ] I've discussed this with core contributors already. ## Detailed Description of the Pull Request / Additional comments The selection with shift is quite broken in 1.6. It started with #8611 that introduces cell selection on `shift+click`. This change resulted in the following defect: `shift+double-click`, `shift+triple-click` select only parts of the word. The reason for this is that the first `shift+click` establishes the selection, while the consequent clicks simply extend it to the relevant boundary (aka word / line boundary) However, the logic was broken even before #8611. For instance, `shift+triple-click` had exactly the same handicap: `shift+double-click` was establishing the selection and the third click was simply extending it to the line boundary. This PR addresses the both defects in the following manner: upon multi-click that starts new selection we establish a new selection on every consequent click using appropriate mode (cell/word/line) rather than trying to extend one. For this purpose we remember the position that started the selection. (cherry picked from commit 83f2a3b)
## PR Checklist * [x] Closes #9382 * [x] CLA signed. * [ ] Tests added/passed * [ ] Documentation updated. * [ ] Schema updated. * [ ] I've discussed this with core contributors already. ## Detailed Description of the Pull Request / Additional comments The selection with shift is quite broken in 1.6. It started with #8611 that introduces cell selection on `shift+click`. This change resulted in the following defect: `shift+double-click`, `shift+triple-click` select only parts of the word. The reason for this is that the first `shift+click` establishes the selection, while the consequent clicks simply extend it to the relevant boundary (aka word / line boundary) However, the logic was broken even before #8611. For instance, `shift+triple-click` had exactly the same handicap: `shift+double-click` was establishing the selection and the third click was simply extending it to the line boundary. This PR addresses the both defects in the following manner: upon multi-click that starts new selection we establish a new selection on every consequent click using appropriate mode (cell/word/line) rather than trying to extend one. For this purpose we remember the position that started the selection. (cherry picked from commit 83f2a3b)
🎉This issue was addressed in #9403, which has now been successfully released as Handy links: |
🎉This issue was addressed in #9403, which has now been successfully released as Handy links: |
Environment
Steps to reproduce
I updated from Microsoft WindowsTerminal 1.5.10271.0 to 1.6.10571.0 and have been using the following configuration for wordDelimiters
"wordDelimiters": " ()\"':,;<>~!@#$%^&*|+=[]{}~?│"
.With 1.5.10271.0, the wordDelimiters were honored in both my Ubuntu WSL 1 zsh shell (double click left mouse button), and inside tmux (shift + double click left mouse button).
With 1.6.10571.0, the wordDelimiters are honored in my Ubuntu WSL 1 zsh shell (double click left mouse button), but not inside tmux (shift + double click left mouse button). Holding the shift key and double clicking to select text from within tmux only partially selects text (such as entire words), and doesn't honor the wordDelimiters confugration.
Expected behavior
The expected behavior is that selecting text from within tmux with (shift+double click left mouse button) works as it did in Microsoft WindowsTerminal 1.5.10271.0.
Actual behavior
The actual behavior is that selecting text from within tmux with (shift+double click left mouse button) only partially selects text with Microsoft WindowsTerminal 1.6.10571.0.
The text was updated successfully, but these errors were encountered: