liteide
liteide copied to clipboard
visualfc
Key Mapping
Please answer these questions before submitting your issue. Thanks! Please download LiteIDE latest version and test before submitting your issue. Thanks!
What version of LiteIDE are you using (LiteIDE About - Version and Build Qt Version)?
source 33.3 compiled against Qt 5.10.1
What version of Go are you using (go version)?
10.2
What operating system and processor architecture are you using(go env)?
OSX Sierra using standard PC keyboard.
Setting Key mapping of:
GotoDocEnd: Ctrl+End GotoDocStart: Ctrl+Home GotoLineEnd: End GotoLineStart: Home
These do not work on OSX. Home will work for a little bit, then loses its mapping, and starts to jump to the beginning of the doc or the end of the doc for END key.
GotoLineStart does not work, it puts the cursor on the first letter of the code, not the actual beginning of the line.
but the original default mapping of: Ctrl+RightArrow will take to the end of the line and Ctrl+LeftArrow will take to the beginning of code.
GotoLineStart should ignore the code and go to the beginning of the line. Key mappings should not lose their stickiness and not revert to default.
I agree and have the same issue. It doesn't seem to be possible to map to GotoLineEnd to the 'End' -key and GotoLineStart to the 'Home' -key. I am using the larger Mac keyboard (with the numeric pad) and there doesn't seem to be a way to map the Home and End key properly.
Sublime has the same issue，but it can be redefined. Preferenct -> Key Bindings
[ { "keys": ["home"], "command": "move_to", "args": {"to": "bol", "extend": false}}, { "keys": ["end"], "command": "move_to", "args": {"to": "eol", "extend": false} }, { "keys": ["shift+home"], "command": "move_to", "args": {"to": "bol", "extend": true}}, { "keys": ["shift+end"], "command": "move_to", "args": {"to": "eol", "extend": true} }, ]
Anything help ?
This exact issue exists LiteIDE X36.3 on macOS Catalina 10.15.3
This is a bug introduced in the lite IDE code at some point as I was using an earlier version (not sure which version) and it worked just fine but now after "upgrading" this is the behavior.
For me at least this is a non-starter I'm going to have to move to a different IDE
