Re: time builtin handles backgrounding poorly
On Thu, Sep 13, 2007 at 10:21:26PM -0400, Chet Ramey wrote: > > `time' is not a builtin; it is a shell reserved word that causes timing > information to be printed when `waitpid' returns. It's a synchronous > operation that doesn't interact as you'd like with job control. Ah, I see. Is there any recommended way to disable time entirely? alias time="command time" seems to work, just wondering if there is a better solution. -Jack
Re: time builtin handles backgrounding poorly
Jack Lloyd wrote: > On Thu, Sep 13, 2007 at 10:21:26PM -0400, Chet Ramey wrote: >> `time' is not a builtin; it is a shell reserved word that causes timing >> information to be printed when `waitpid' returns. It's a synchronous >> operation that doesn't interact as you'd like with job control. > > Ah, I see. Is there any recommended way to disable time entirely? Reconfigure bash with `--disable-command-timing' and rebuild. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
Re: Process Substitution backgrounds the command list?
Chet Ramey wrote: > No, there's no way to wait for it. Hmm... That does make it very difficult to actually use correctly. If there are any practical uses I am missing seeing them. Any useful examples? Is that enough of a misfeature to qualify as a bug? Bob
