Skip to main content
replaced http://superuser.com/ with https://superuser.com/
Source Link

I propose that we leave them as-is, and teach the users to avoid the insanity of editing complex commands directly in the shell. Bash, for one, allows us to edit the current command in an editoredit the current command in an editor by pressing CtrlxCtrle (via the readline library).

I propose that we leave them as-is, and teach the users to avoid the insanity of editing complex commands directly in the shell. Bash, for one, allows us to edit the current command in an editor by pressing CtrlxCtrle (via the readline library).

I propose that we leave them as-is, and teach the users to avoid the insanity of editing complex commands directly in the shell. Bash, for one, allows us to edit the current command in an editor by pressing CtrlxCtrle (via the readline library).

edited body
Source Link
muru
  • 204k
  • 2
  • 41
  • 67

I propose that we leave them as-is, and teach the users to avoid the insanity of editing complex commands in directly in the shell. Bash, for one, allows us to edit the current command in an editor by pressing CtrlxCtrle (via the readline library).

I propose that we leave them as-is, and teach the users to avoid the insanity of editing complex commands in directly the shell. Bash, for one, allows us to edit the current command in an editor by pressing CtrlxCtrle (via the readline library).

I propose that we leave them as-is, and teach the users to avoid the insanity of editing complex commands directly in the shell. Bash, for one, allows us to edit the current command in an editor by pressing CtrlxCtrle (via the readline library).

Source Link
muru
  • 204k
  • 2
  • 41
  • 67

I propose that we leave them as-is, and teach the users to avoid the insanity of editing complex commands in directly the shell. Bash, for one, allows us to edit the current command in an editor by pressing CtrlxCtrle (via the readline library).