Re: BUG: "time" command adding to wrong process.

[James Bonfield]

On Wed, Jan 08, 2014 at 10:50:47AM -0500, Chet Ramey wrote:
> It's more difficult to get timing information for other individual
> processes, and changing the code to do that would interfere with the
> ability to time builtins and other shell commands.

Understood. Perhaps it just needs a line in the documentation
suggesting that in complex pipelines it would be advisable to start
subshells for any time commands. Ie "(time foo)" instead of "time
foo".

Regards,

James

-- 
James Bonfield (jkb@sanger.ac.uk) | Hora aderat briligi. Nunc et Slythia Tova
                                  | Plurima gyrabant gymbolitare vabo;
  A Staden Package developer:     | Et Borogovorum mimzebant undique formae,
https://sf.net/projects/staden/   | Momiferique omnes exgrabure Rathi. 


-- 
 The Wellcome Trust Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE.