home | list info | list archive | date index | thread index

Re: [OCLUG-Tech] is "xargs" really still useful just for limiting command line size?

  • Subject: Re: [OCLUG-Tech] is "xargs" really still useful just for limiting command line size?
  • From: Peter Sjöberg <peters-oclug [ at ] techwiz [ dot ] ca>
  • Date: Tue, 20 Mar 2018 11:34:12 -0400
On 2018-03-16 11:39 AM, Brett Delmage wrote:
> On Fri, 16 Mar 2018, J C Nash wrote:
> 
>> This may introduce a tangent, but I find the limit is often not the
>> coded one but issues related to
>> - getting 250 characters into the line and not remembering whether the
>>   parameter should be X or x and what the difference is.
> 
> Indeed.
> 
> For those who may not be familiar, "<Esc>#" is a useful key combo in
> bash for this situation. I was delighted to discover it.
> 
> It immediately puts a "#" comment character at the start of your line
> then submits it as if you had pressed enter. The incomplete command is
> then in your command line buffer as a comment. You can look up the
> missing info you need, then retrieve your command line using the Up
> arrow key or ^R, then carry on completing and submitting it after
> deleting the "#".
> 
> Kind of like a ^Z suspend for the command line.

Didn't know about <ESC># but using <Home># all the time