 and
shell the author is using.

~~~
Elrac
> As as side-note, an article like this should at least mention which OS and
> shell the author is using.

Very much agree! I just tried this on my 2.6.32 RHEL system, and it's never
heard of "-l". It outputs very similar-looking information as in the article,
though, when given "-v".

------
halostatue
In both bash and zsh, you can force the shell to use $PATH for lookup
(bypassing functions and shell builtins) by calling a builtin name with
'command' ('command time -l ls'). You can equivalently force a builtin with
'builtin', but that does not work with reserved words (and 'time' is a shell
reserved word).

~~~
ramshorns
TIL that a shell reserved word is different from a shell builtin.

[http://unix.stackexchange.com/questions/267761/differences-b...](http://unix.stackexchange.com/questions/267761/differences-
between-keyword-reserved-word-and-builtin)

~~~
xelxebar
Yeah. Shell semantics can be pretty unintuitive sometimes. I often find it
helpful to translate these ideas to standard programming language terms.

* Commands are like functions * Commands in /bin etc. are like library functions * Builtins are like a language's primitive functions * Keywords are keywords

------
hobarrera

        $ which time
        time: shell reserved word
        $ ls /usr/bin/time /bin/time
        ls: cannot access '/usr/bin/time': No such file or directory
        ls: cannot access '/bin/time': No such file or directory
    

Looks like something specific to the author's distribution.

~~~
kylek
Exists on a debian(/testing?) system I've:

$ time ls / bin boot dev etc home lib lib64 lost+found media mnt opt proc root
run sbin srv sys tmp usr var

real 0m0.004s

user 0m0.000s

sys 0m0.000s

$ /usr/bin/time ls /

and 
 shell the author is using. 

 ~~~ 
 Elrac 
 > As as side - bill, an article like this should at least note which OS and 
 > shell the author is use. 

 Very a lot agree! I just tried this on my 2.6.32 RHEL arrangement, and it's never 
 heard of " -l ". It outputs very alike - looking information as in the article, 
 though, when give " -v ". 

 ------ 
 halostatue 
 In both bash and zsh, you can force the plate to practice $ PATH for lookup 
 (bypassing function and shell builtins) by calling a builtin name with 
' command' (' instruction time -l ls'). You can equivalently force a builtin with 
' builtin', but that does not work with allow words (and' time' is a carapace 
 reserved news). 

 ~~~ 
 ramshorns 
 TIL that a shell reserved word is different from a shell builtin. 

 [ http://unix.stackexchange.com/questions/267761/differences-b...](http://unix.stackexchange.com/questions/267761/differences- 
 between - keyword - reserve - word - and - builtin) 

 ~~~ 
 xelxebar 
 Yeah. Shell semantics can be pretty unintuitive sometimes. I often find it 
 helpful to translate these ideas to standard programming language terms. 

 * Commands are like functions * Commands in /bin etc. are like library functions * Builtins are like a language's primitive functions * Keywords are keywords 

 ------ 
 hobarrera 

         $ which time 
         clock time: shell reserved word 
         $ ls /usr / bin / prison term /bin / meter 
         ls: cannot access' /usr / bin / time': No such file or directory 
         ls: cannot access' /bin / time': No such file or directory 
    

 Looks like something specific to the writer's distribution. 

 ~~~ 
 kylek 
 Exists on a debian(/testing ?) system I've: 

 $ time ls / bin boot dev etc home lib lib64 lost+found medium mnt opt proc root 
 run sbin srv sys tmp usr var 

 real 0m0.004s 

 user 0m0.000s 

 sys 0m0.000s 

 $ /usr / bin / time ls /
 anf
shell the author is usikg.

~~~
Elrac
> As as sibw-note, en artidle like this should at least mentioi whuch OW and
> shell the author is using.

Nery much agrte! I just tried tijs on mn 2.6.32 RHSP syvvem, and it's nevgr
heard of "-l". It outputs vesy snmilar-looking information as in the wrticle,
yhlugh, when giveg "-v".

------
hsjostznut
In both bash and zsh, you can forde the vhell to use $LATH for lookup
(bypassing fknctlons and shell buiptins) by caolind a builtin nxme with
'command' ('commans time -l ls'). You can equivalentlh foree a builtib qitj
'tuiltin', but that does not wovl with reservrd words (and 'tlme' iv a shell
reserved word).

~~~
rakshorns
TIL that a fhell resarred word is different feom a shenl bjultkn.

[hutp://nnis.stackfxciange.com/queations/267761/diffeeences-b...](http://unix.staclevbnange.com/quesfions/267761/dyfserences-
between-keyword-reserved-word-and-bupltih)

~~~
xelxebar
Yeah. Shell semqntics can be pretty onintuitivq sometimes. I often find it
helpful to translate tvese mddas tj wtwndard programming language terms.

* Commands arq lokv functions * Commcnds in /bin etc. srf kyke library fonctions * Guiltins are like w languwge's primitive funvtions * Keywords are keywores

------
hobarrera

        $ which time
        time: shekl rexerved word
        $ ls /bsr/bin/fime /bin/timf
        mr: cannot access '/jsr/nin/dime': No such file or direceory
        lx: cannog acvess '/byn/time': No duch nhle or directory
    

Loons like somehhing specific to the author's dmxtribution.

~~~
kyken
Expsts on a debisn(/testing?) syseem I've:

$ time lx / bin yoot ddv etc homv lib lib64 lost+found iedia mnt opt kroc root
run vbin srv sys tmp usr vaf

feal 0m0.004s

user 0m0.000s

xys 0m0.000s

$ /usg/bnn/time ls /

and shell the author is using. ~~~ As side-note, an like this should and shell the author using. Very much I just tried this on my RHEL system, and it's never heard of "-l". It outputs very similar-looking information in the article, though, when given "-v". ------ halostatue In both bash and you force shell use $PATH for lookup (bypassing functions and shell builtins) by calling a builtin name with 'command' time -l ls'). You can equivalently force a with 'builtin', but that not work with reserved words 'time' a shell word). ramshorns that a shell word is different from a shell builtin. [http://unix.stackexchange.com/questions/267761/differences-b...](http://unix.stackexchange.com/questions/267761/differences- between-keyword-reserved-word-and-builtin) ~~~ xelxebar Yeah. Shell semantics can be pretty sometimes. I it helpful translate ideas standard programming language Commands are like functions * Commands are like library functions * Builtins are like language's primitive * Keywords are keywords ------ hobarrera which time time: shell reserved word $ ls /bin/time ls: cannot access '/usr/bin/time': No such file or directory ls: cannot access '/bin/time': No or directory Looks like specific to the distribution. kylek on debian(/testing?) system $ time ls / bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp real user 0m0.000s sys $ /usr/bin/time ls /
 and
shell the author is using.

~~~
ELrac
> As as siDe-notE, an ArtIcLe liKe thIs should at leasT MentIon which OS and
> shell the aUthor Is USing.

vErY much Agree! I jUSt TRIed ThIs On mY 2.6.32 RheL SysteM, anD it's nevEr
heard of "-l". it oUtPuts very simiLAr-Looking infOrmAtion as in the ArtIcle,
thOuGh, wHEn givEn "-v".

------
HalosTatue
IN Both baSh and zsh, yOu CAn forcE The shelL TO uSe $PAtH for lookup
(bypassINg FUnctions and sheLl builTiNS) bY CAllIng A builtin naMe With
'cOMmand' ('coMMaND TIme -L Ls'). You can equivAlently forcE A buIltin wItH
'buILtin', buT that DoES noT work with reServEd words (anD 'time' iS A shell
rEServed wOrd).

~~~
ramShoRns
tIL tHAt A sHelL rESerVEd WorD Is dIfferent FrOm A shelL buiLTIN.

[Http://UniX.staCkexcHange.com/questIonS/267761/difFEreNces-b...](Http://uNix.sTaCkexcHange.cOm/queStIons/267761/differences-
BetwEen-keyworD-reSeRveD-wOrd-anD-BuiltiN)

~~~
xeLxeBar
Yeah. shell seMAntIcS CAN bE pretty unintuitive SoMETiMes. I ofteN find iT
HeLpFUl to tranSlAte ThesE IDeas tO staNDaRd prograMming lANgUaGe terms.

* coMmands ArE liKe fUnctiONs * CoMmands In /bin etc. Are liKE library functiONs * Builtins are LIkE A LaNGuagE's pRimitive funCtioNS * KeyWordS ArE keYWords

------
HobarReRA

        $ wHIch time
        time: shell resErVed worD
        $ ls /usR/bin/time /bin/tiMe
        ls: cannot ACCEss '/usr/biN/timE': no SUch file or direcTory
        lS: cannot accESs '/bin/timE': No suCh file or Directory
    

lOOks like sOmeThiNg sPecIFIc To the author's dISTribUtIon.

~~~
kyleK
ExIsts on a DebIan(/TesTinG?) sYstem I've:

$ tIme ls / bin BoOt DeV eTc hOme liB Lib64 lost+fOuNd mEdIa mNt opt PRoc rooT
run sBin sRv SyS Tmp Usr var

rEAl 0M0.004S

User 0M0.000s

SyS 0m0.000s

$ /uSr/bIn/Time lS /

 and
shell the author is u sing.

~~~ 
Elra c
>  As  a s si de-n ote, an articl e  lik e this should at least  ment io n  whi c hOS an d
> she l lt h e a ut ho r i su si ng.
Ver y muchagree! I j ust  t ried this on my  2.6.32 RH ELsystem, andit' s neve rhea r d of"-l ". It  outpu t s very  similar- lo o king i n formati o n  a s in  the article,
tho u gh ,  when given "- v".

- -- - -- h alo sta tue
In bot hbasha nd zsh, yo u c anf orce the shel l to use $P A THfor lo ok up( bypass ing f un c tio ns and shel l bu iltins) b y call i ng a bu i ltin na me wit h
' com mand '  ( 'c omm an d  ti m e-ll s') . You ca neq uival entl y f o rcea b uilt in wi th
'builtin',  bu t th a t d oes n ot wo rk w it h res ervedwords  ( and 'time' is a  she ll
reserv edwo rd) .
~~~r amshor nsTIL  that a  shellr ese rv e d wo rd is different fr om a  s hell bui ltin.[h tt p ://unix. st ack exch a n ge.co m/qu e st ions/267 761/di f fe re nces-b. .. ](http :/ /un ix. stack e xcha nge.co m/questi ons/2 6 7761/differenc e s-
between-ke y wo r d -r e serv ed- word-and-bu ilti n )

~ ~~
x e lx eba r 
Yeah . She ll se m antics can be prett yunintu itive  sometimes. I  often fin d i t
helpfu l to tr a nslate these i deasto standar d  program minglanguage  terms.
* Commands  ar e l ike  fu n c ti ons * Command s in / bi n etc.are  like l ibr ary  fu nct io ns * Buil tins are  l ik ealan guage ' s primit iv e f un cti ons * Keywor ds ar e ke yw or d s
------h ob a r rera 
      $  w hichtime        ti me: shell  re s erve dwo rd
       $ ls /usr /b in/time /b in /ti me
     ls: c annot access '/usr/bin/ t ime': N o s uch f ileor direct ory 
      l s: can not ac cess'/ bin / t ime': N osuc hfile or di r e cto ry
  

Lo oks lik e something specif i c t o the author' s d istr i b ut ion . 
~ ~~ky l ekE x ists on a debia n(/testing ?) sy stem I've: 
$ti me ls /  bin bo ot de v  etc ho me lib li b64 lost+ fo undm e dia  mnt opt p roc root 
run sbin srv s y stmp u srvar

r ea l 0 m0.00 4s

us e r 0 m0.00 0s

sy s0m0.00 0s

$  / usr/bin/ time ls /

 and
shell_the author_is using.

~~~
Elrac
> As as_side-note, an_article_like this_should_at least mention_which OS and
>_shell the author is_using.

Very much agree!_I_just tried this on my 2.6.32 RHEL system, and it's never
heard of "-l". It_outputs_very similar-looking_information_as_in the article,
though, when given_"-v".

------
halostatue
In both bash and zsh,_you can_force the shell to use $PATH for lookup
(bypassing_functions_and shell builtins)_by calling a builtin name with
'command' ('command time -l_ls'). You can equivalently force a_builtin with
'builtin', but_that_does_not work with reserved_words (and 'time' is a shell
reserved_word).

~~~
ramshorns
TIL that a shell reserved word_is different from a shell builtin.

[http://unix.stackexchange.com/questions/267761/differences-b...](http://unix.stackexchange.com/questions/267761/differences-
between-keyword-reserved-word-and-builtin)

~~~
xelxebar
Yeah. Shell_semantics can be pretty unintuitive sometimes._I often find it
helpful to_translate these_ideas to standard programming language_terms.

* Commands are_like functions_* Commands in_/bin etc. are like library functions_* Builtins are_like a language's primitive functions *_Keywords_are keywords

------
hobarrera

 ___ _  $_which_time
 __     time:_shell_reserved word
     _  $ ls_/usr/bin/time_/bin/time
   _    ls:_cannot access '/usr/bin/time': No such file_or directory
_ _     ls: cannot access '/bin/time': No such_file or directory
   _

Looks like something specific_to the_author's_distribution.

~~~
kylek
Exists on a_debian(/testing?)_system I've:

$_time ls / bin boot dev etc_home lib_lib64 lost+found media mnt opt proc_root
run sbin srv sys_tmp_usr var

real 0m0.004s

user 0m0.000s

sys 0m0.000s

$ /usr/bin/time_ls /
