Bug #50085 | Shift + Alt + Arrow key does not select whole words in SQL Editor | ||
---|---|---|---|
Submitted: | 5 Jan 2010 10:03 | Modified: | 23 Aug 2011 19:39 |
Reporter: | Simon Hambly | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.11 beta | OS: | MacOS (10.5.8) |
Assigned to: | CPU Architecture: | Any |
[5 Jan 2010 10:03]
Simon Hambly
[5 Jan 2010 10:33]
Johannes Taxacher
this sounds like a problem in the scintilla framework we're using for the sql editors. might take some effort to dig into that.
[5 Jan 2010 10:53]
Susanne Ebrecht
This seems to be OS related. ALT + Arrow just moves the cursor one step here and SHIFT-ALT-Arrow marks step by step with the cursor. What exactly is your feature request now?
[5 Jan 2010 12:39]
Simon Hambly
The Alt + Arrow is the standard Mac shortcut key combination (the equivalent to Ctrl + Arrow in Windows) for moving a word at a time. The Shift + Alt + Arrow is also a standard Mac shortcut (for selecting word at a time). I would expect cross-platform software to support/respect native OS shortcut keys. What puzzles me is why the SQL Editor understands Alt + Arrow but not Shift + Alt + Arrow.
[5 Jan 2010 15:51]
Valeriy Kravchuk
Verified just as described. Indeed, this is against usual Mac UI behavior.
[23 Aug 2011 19:39]
Philip Olson
Fixed as of 5.2.34, and here's the documentation entry: On Mac OS X, the <keycap>Shift+Alt</keycap> + <keycap>Arrow</keycap> combination selected individual characters instead of words.
[11 Mar 2015 18:23]
Chen Guo
This bug still exists with the latest Mac OS Yosemite. Shift + Alt + Arrow only selects one character instead of one word.
[19 May 2015 18:16]
Christian Kopp
This bug has reappeared in the latest version 6.3.3 (64bit)
[2 Jun 2015 14:19]
Danilo Gonçalves
Confirmed as broken on 6.3.3 (64bit) with OS X Yosemite 10.10.3
[23 Sep 2015 17:15]
Philip Olson
There was a regression here, and a proper fix took place in MySQL Workbench 6.3.5. See also MySQL Bug #76526 Thank you for the comments.