Timeline for How to run previous command with another command
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 22, 2023 at 5:41 | comment | added | Nickotine | can you give an example please? | |
| Nov 22, 2023 at 3:53 | comment | added | Stephen Harris | No, the <ESC>. is purely a command line "insert at this point the last word". It actually shows up as if you've typed the last word. It doesn't open an editor at all. | |
| Nov 22, 2023 at 3:51 | comment | added | Nickotine |
are there any advantages or use cases where your 2nd option would be better? So do you mean for your emacs example that if I done ls <ESC> emacs would open with the ls output written in?
|
|
| Nov 22, 2023 at 3:42 | comment | added | Stephen Harris |
Also, depending on your shell editing mode... if you've done set -o emacs then <ESC>. will bring the last word in. So ls <ESC>. I'm not sure there's an equivalent in vi mode, but I could be wrong.
|
|
| Nov 22, 2023 at 3:38 | history | edited | Stephen Harris | CC BY-SA 4.0 |
added 181 characters in body
|
| Nov 22, 2023 at 3:25 | comment | added | Nickotine |
Damn I should've known that, I use $_ a lot.
|
|
| Nov 22, 2023 at 3:24 | vote | accept | Nickotine | ||
| Nov 22, 2023 at 3:15 | history | answered | Stephen Harris | CC BY-SA 4.0 |