- 1 Vapor IO Brings OpenDCRE to General Availability
- 2 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 3 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 4 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 5 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
Bash Command Line Shortcuts
Here, are a few useful candidates.
(C = control key, M = alt/meta key.)
- C-r and C-s : Launch an incremental search backward and forward (respectively), in your command-line history.
- C-j and C-g : Abandon an incremental search either with the line found, or with the original line (respectively).
- M-. or ESC then . : Both of these insert the final argument to the last command at the cursor point. This is useful when moving files around and editing them.
- M-C-y : Insert the first argument to the previous command at the cursor point. If you want the nth argument, hit M-n beforehand. So M-2 M-C-y would give you the 2nd argument to the previous command. (A lot of keys to remember, but it's useful once in a while.)
- C-w and M-backspace : Both delete the word behind the cursor. C-w uses whitespace as a boundary, whereas M-backspace uses non-alphanumeric characters. So if you have file.txt and hit C-w, you'll delete the lot, whereas M-backspace would leave you with file.. This has very obvious uses. (It also works with underscores.)
I learned some new shortcuts while researching this, so hopefully you learned something useful, too!
Ed Note: A quick note about the Perltidy tip from a fortnight ago. Thanks to Randal L. Schwartz for pointing out it's a good idea to set up tests for your code, to check that it does the same thing after Perltidy is finished as it did before. As he discusses here, ultimately the only thing that can interpret Perl code entirely reliably is the Perl interpreter itself. So be aware that there are circumstances in which Perltidy (and similar programs) can break code!