![]() ![]() For example, gdb also uses Readline to process input. ![]() And so to say, it is very convenient to know Readline bindings since it is used not only in bash. It uses Readline library to implement command line input. What you actually want is a fast way to navigate over command line in you shell program. To be clear, you don't want a "fast way to move the cursor on a terminal command line". There must be a way to search and jump directly to the part I need to modify, e.g. But on a long line that takes too much time. What is the fastest way to get there? What I usually do is Ctrl- A to get to the beginning and then repeatedly Alt- F to move forward, word by word (or Ctrl- E to go the end and Alt- B to then go backward). Now I need to move (starting from the beginning or the end of the line) the cursor to -option25 to modify something there. cmd -option1 -option2 -option3 -option4 -option5 -option6 -option7 -option8 -option9 -option10 -option11 -option12 -option13 -option14 -option15 -option16 -option17 -option18 -option19 -option20 -option21 -option22 -option23 -option24 -option25 -option26 -option27 -option28 -option29 -option30 -option31 -option32 -option33 -option34 -option35 -option36 -option37 -option38 -option39 -option40 -option41 -option42 -option43 -option44 -option45 -option46 -option47 -option48 -option49 -option50 Say I used the arrow key or Ctrl- R to get this long command line. You can get it from here: wget -O fix-shortcuts.What is the best way to move around on a given very long command line in the terminal? # To disable resetting a value, just comment out the line "/org/gnome/desktop/wm/keybindings/begin-resize" "/org/gnome/desktop/wm/keybindings/begin-move" "/org/gnome/desktop/wm/keybindings/switch-to-workspace-right" "/org/gnome/desktop/wm/keybindings/switch-to-workspace-left" "/org/gnome/desktop/wm/keybindings/switch-to-workspace-up" "/org/gnome/desktop/wm/keybindings/switch-to-workspace-down" "/org/gnome/settings-daemon/plugins/media-keys/terminal" "/org/gnome/settings-daemon/plugins/media-keys/screensaver" "/org/gnome/desktop/wm/keybindings/toggle-shaded" Readonly BACKUP_FILE="undo-fix-shortcuts-$(date +%s%N).sh" # shortcuts disabled, comment them out in the `KEYS` array. # Creates a backup file to restore the previous settings. # Disables Ubuntu shortcuts that clash with IntelliJ Idea (and probably other To not have some shortcuts disabled, comment them out in the KEYS array. It also creates a backup file so that you can restore your previous settings. I have created this script that disables all clashing shortcuts between Ubuntu (tested with 15.10) and IntelliJ (and probably more Jetbrains products). Just refer to How can I restore default keyboard shortcuts?, in case if you're lost. Note: You can always revert Ubuntu shortcuts back to its default state. Change or disable the Resize window action, assigned to Alt + F8 (Evaluate expression).Disable the Move window action, assigned to Alt + F7 (Find usages).Change or disable the Switch to workspace action, assigned to Ctrl + Alt + Arrow Keys (Navigation).Change or disable the Launch terminal action, assigned to Ctrl + Alt + T (Surround with).Change or disable the Lock Screen action, assigned to Ctrl + Alt + L (Reformat code). ![]() Disable the Shade window action, assigned to Ctrl + Alt + S (Settings dialog).Here’s a list of tweaks you need to make with default system key bindings so that they won’t interfere with IntelliJ IDEA actions (listed in brackets). Also, I've managed to find to keymap settings: What it means is that a user can work with it without touching the mouse. As a bit of reading taught me, Intellij IDEA is a keyboard-centric IDE. ![]()
0 Comments
Leave a Reply. |