-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Add keyboard shortcuts for moving blocks #10455
Comments
Ulysses uses |
@mtias What would the Linux/Windows equivalent of those be? |
Are there any moves forward with this one? It would really mean improvements in usability. Imagine a 2000 word-long article where you have to duplicate some paragraphs and move them to the bottom. Now I have 2 options:
It would be a lot more comfortable if I could move it up/down with pressing some keys on my keyboard (e.g. simulating the clicks on the arrows). |
+1 Amazed this isn’t implemented yet. |
I frequently stumble upon this issue as well. The main issue is when the arrow icons change their position on the display slightly, leading to a lot of missclicks. I tested some expected shortcuts (Windows: arrow keys with either cmd, alt or shift) and was surprised it's not implemented. The following google search led me here. |
I would love this! I don't want to keep clicking. |
Dropbox Paper also uses ⌃⌘↑ and ⌃⌘↓. Big 👍🏻 |
There's also copy paste. |
It's worth noting that, on a keyboard, after you've focused one of the movers, you can just press Space to press it. (This works for all HTML |
And this one is in progress: #22031 |
The issue
Currently, there is no way to move a block when the side controls are not shown. Ideally, there should be keyboard shortcuts for moving blocks up and down.
Proposed solution
In #71 I noticed that the following was suggested as the macOS shortcut:
Move block up: ^Ctrl+⌥Option+↑
Move block down: ^Ctrl+⌥Option+↓
If these were used, the Windows and Linux equivalents would be:
Move block up: ⇧Shift+⎇Alt+↑
Move block down: ⇧Shift+⎇Alt+↓
The text was updated successfully, but these errors were encountered: