Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14710 > unrolled thread

Re: Command not found with builtins and variables

Started byChet Ramey <chet.ramey@case.edu>
First post2018-10-11 10:43 -0400
Last post2018-10-11 10:43 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Command not found with builtins and variables Chet Ramey <chet.ramey@case.edu> - 2018-10-11 10:43 -0400

#14710 — Re: Command not found with builtins and variables

FromChet Ramey <chet.ramey@case.edu>
Date2018-10-11 10:43 -0400
SubjectRe: Command not found with builtins and variables
Message-ID<mailman.2020.1539269008.1284.bug-bash@gnu.org>
On 10/10/18 6:52 PM, Bob Proulx wrote:
> Chet Ramey wrote:
>> bugs@feusi.co wrote:
>>> The thing I noticed is that when setting a variable and then running the
>>> command "time", bash reports "command not found". For example, the
>>> command:
>>>
>>> TEST=1 time ls
>>>
>>> Results in "bash: time: command not found"
> 
> That would work if you installed the GNU time package.

Maybe. Maybe not. It depends on $PATH. It's unlikely that his system
does not already have a `time' command, so if it's not found, it must
not be in $PATH.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web