Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14707 > unrolled thread
| Started by | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| First post | 2018-10-10 11:17 -0400 |
| Last post | 2018-10-10 11:17 -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.
Re: Command not found with builtins and variables Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-10 11:17 -0400
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2018-10-10 11:17 -0400 |
| Subject | Re: Command not found with builtins and variables |
| Message-ID | <mailman.1957.1539184676.1284.bug-bash@gnu.org> |
On Wed, Oct 10, 2018 at 01:42:50PM +0200, bugs@feusi.co wrote: > TEST=1 time ls time is not a builtin. It's a "keyword". It's a piece of the shell's syntax. It has special magical rules that apply to nothing else. If you want to set an environment variable in the temporary execution environment of a command, and time how long that command takes, then you write it like this: time TEST=1 something that is not actually ls because ls does not use \$TEST > TEST=1 cd > > Works without any problems, Completely useless. cd does not use environment variables. Stop OBFUSCATING your questions. Post the ACTUAL QUESTIONS with the ACTUAL INTENT so we can answer them.
Back to top | Article view | gnu.bash.bug
csiph-web