Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14710
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Command not found with builtins and variables |
| Date | 2018-10-11 10:43 -0400 |
| Message-ID | <mailman.2020.1539269008.1284.bug-bash@gnu.org> (permalink) |
| References | <20181010114208.GB5122@feusi.co> <2c90cb43-981e-0b5f-fd35-61d449244eb1@case.edu> <20181010163035678665001@bob.proulx.com> |
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/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Command not found with builtins and variables Chet Ramey <chet.ramey@case.edu> - 2018-10-11 10:43 -0400
csiph-web