Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bug: Ctrl-T on Mac should transpose characters
See original GitHub issueIn a native Mac text field, pressing Ctrl-T will transpose the adjacent characters and move one character rightwards. i.e. given
a b c
^ cursor
pressing Ctrl-T will give
b a c
^ cursor
This shortcut doesn’t work in Lexical. Reproed on lexical.dev and in Workplace UFI.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Ctrl-t (transpose) command inserts extra character. #8574
This seems to have gotten worse recently; occasionally ctrl-t will cause multiple lines of text below the cursor to get duplicated into the...
Read more >Change the behavior of the modifier keys on Mac
You can change the action that modifier keys, such as Control or Option, perform when you press them. On your Mac, choose Apple...
Read more >Universal Control Not Working? Here's How to Fix It
This article offers solutions to the most common problems encountered when getting Universal Control to work. universal control. With Universal ...
Read more >Weird characters appear when pressing command-A,C,V
It looks like you have accidentally configured your control key to be your alt key. Case in point: when I press alt +...
Read more >Action to transpose characters : IDEA-80498
In vim you can do this with "xp" in normal mode. In kdevelop/kate/kwrite you can do this using ctrl+t. It's kind of small...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Nice. I noticed that Ctrl-K (also an emacs keybinding) seems to behave incorrectly in Lexical as well. It should delete to (but not including) the nearest \n (or end of string), or delete one \n if you’re right before one. In Lexical it seems to be also deleting the newline and some of the characters from the next line, depending on your cursor position when pressing it.
Closing in favour of #2769