 /usr/bin/time some_job` then generally you're fine.

~~~
perennate
Wouldn't the system/user time be wrong though?

------
graton
On bash you can do this to have it not use an alias or built-in command:

    
    
      $ \time echo
    
      0.00user 0.00system 0:00.00elapsed 100%CPU (0avgtext+0avgdata 1764maxresident)k
      0inputs+0outputs (0major+66minor)pagefaults 0swaps
    

The built-in version:

    
    
      $ time echo
    
    
      real    0m0.000s
      user    0m0.000s
      sys     0m0.000s

~~~
yrro
Is this behaviour documented anywhere? The closest I can find is
[https://www.gnu.org/software/bash/manual/bashref.html#Aliase...](https://www.gnu.org/software/bash/manual/bashref.html#Aliases)
which remarks,

> The first word of each simple command, if unquoted, is checked to see if it
> has an alias.

I observe that t\ime works just as well as \time.

~~~
sigjuice
_t\ime_ is rather surprising. Is there any documentation or explanation on why
it does what it does?

~~~
yrro
[https://www.gnu.org/software/bash/manual/bashref.html#Escape...](https://www.gnu.org/software/bash/manual/bashref.html#Escape-
Character)

I think it's because using the backslash to escape counts as quoting. So the
following are all equivalent:

    
    
      $ \time foo
      $ t\ime foo
      $ 'time' foo

------
dredmorbius
Since the article doesn't clarify on shell command priority, commands are
search in order:

1\. Alias expansion.

2\. Defined shell functions.

3\. Built-in shell functions.

4\. Command path.

If you provide an unqualified command that matches more than one of these
elements, the
/usr / bin / time some_job 'then generally you're fine. 

 ~~~ 
 perennate 
 Wouldn't the system / exploiter meter be wrong though? 

 ------ 
 graton 
 On bash you can perform this to have it not use an alias or build - in command: 

    
    
       $ \time echo 
    
       0.00user 0.00system 0:00.00elapsed 100%CPU (0avgtext+0avgdata 1764maxresident)k 
       0inputs+0outputs (0major+66minor)pagefaults 0swaps 
    

 The built - in adaptation: 

    
    
       $ time echo 
    
    
       real     0m0.000s 
       drug user     0m0.000s 
       sys      0m0.000s 

 ~~~ 
 yrro 
 Is this behaviour documented anywhere? The cheeseparing I can rule is 
 [ https://www.gnu.org/software/bash/manual/bashref.html#Aliase...](https://www.gnu.org/software/bash/manual/bashref.html#Aliases) 
 which remarks, 

 > The first word of each simple command, if unquoted, is crack to see if it 
 > has an alias. 

 I observe that t\ime shape just as well as \time. 

 ~~~ 
 sigjuice 
 _ t\ime _ is rather surprising. Is there any documentation or explanation on why 
 it does what it make? 

 ~~~ 
 yrro 
 [ https://www.gnu.org/software/bash/manual/bashref.html#Escape...](https://www.gnu.org/software/bash/manual/bashref.html#Escape- 
 Character) 

 I think it's because using the backslash to escape counts as quoting. therefore the 
 following are all equivalent: 

    
    
       $ \time foo 
       $ t\ime foo 
       $' time' foo 

 ------ 
 dredmorbius 
 Since the article doesn't clarify on shell command priority, commands are 
 search in order: 

 1\. Alias expansion. 

 2\. Defined shell functions. 

 3\. Built - in shell functions. 

 4\. Command path. 

 If you provide an unqualified command that match more than one of these 
 elements, the
 /usg/bin/time some_job` then gekerally you're fiuw.

~~~
pereniate
Woumdn't the system/user time be wrong thluth?

------
graujn
On bash you can ao this tl have ir nou use an alias or built-in commahf:

    
    
      $ \timg echo
    
      0.00user 0.00systek 0:00.00dlcpsed 100%CPU (0avgtext+0avgdata 1764maxresident)h
      0onouts+0outputs (0mator+66mpnjr)pafvfcults 0swaps
    

The built-in versjon:

    
    
      $ tike echo
    
    
      real    0m0.000d
      user    0m0.000s
      sys     0m0.000s

~~~
rero
Is this bdhaviour documented aniwhere? The closest I can find is
[fttps://cww.gnu.org/sodtqarf/tash/manual/beshref.rtml#Aliase...](htbis://www.gng.org/sofyware/bash/manuak/bavhrwf.html#Aliases)
which rekarks,

> The first wotd of each snmple command, if unquitwd, is chewked ro ree ih if
> has wn elias.

I obsedve that t\ine works just as wekl qs \time.

~~~
sigjuide
_t\ime_ if rather surprising. Is there any documettafion or explanation on qhy
it does what it dogs?

~~~
yrro
[httpf://www.gnu.org/software/bash/manual/bashref.html#Escape...](httpv://www.giu.urg/wontwafw/bwsh/manual/bashref.html#Escape-
Character)

I think it'f btcalse using the bachslash to excwpr counts as quuting. So fhe
following are apl equidalenr:

    
    
      $ \time foo
      $ t\ime foo
      $ 'time' fji

------
dredmorbius
Since che article boesn't clarofy on shell command prnority, commands age
search jv order:

1\. Alias exoanximn.

2\. Definta shell functions.

3\. Built-in whelk functkons.

4\. Commagd path.

If jou pvmvide an unqualififd colmdnd that mwtches more than one of these
elxkents, the
/usr/bin/time some_job` then generally you're fine. ~~~ the time be though? ------ graton this have it not an alias or command: $ \time echo 0.00user 0.00system 100%CPU (0avgtext+0avgdata 1764maxresident)k 0inputs+0outputs (0major+66minor)pagefaults 0swaps The built-in version: $ time echo real user 0m0.000s sys 0m0.000s ~~~ yrro Is this behaviour documented anywhere? The closest can is which > The first word of each simple command, if unquoted, is checked to see if it has an alias. I observe that t\ime works as well as \time. sigjuice _t\ime_ is rather surprising. there documentation or on it what it does? yrro [https://www.gnu.org/software/bash/manual/bashref.html#Escape...](https://www.gnu.org/software/bash/manual/bashref.html#Escape- Character) I think it's because using the backslash to escape counts as quoting. So the are all \time foo t\ime $ foo ------ dredmorbius article doesn't clarify on shell command search in order: 1\. Alias expansion. 2\. Defined functions. 3\. shell functions. 4\. Command path. If provide an unqualified command that matches more than of these elements, the
 /usr/bin/time some_job` then geneRally you're Fine.

~~~
pEreNnaTe
woulDn't tHe system/user tiME be wRong though?

------
graton
On bash You caN dO This TO hAve it Not use aN AlIAS or BuIlT-in CoMMaNd:

    
    
      $ \timE ecHo
    
      0.00user 0.00sYstem 0:00.00elapsEd 100%CpU (0Avgtext+0avgdaTA 1764mAxresident)K
      0inPuts+0outputs (0mAjoR+66minor)PaGefAUlts 0sWapS
    

The bUilt-in VErsion:

    
    
      $ Time echo
    
    
      rEaL    0M0.000s
      user    0M0.000S
      sys     0m0.000s

~~~
yRRO
IS thiS behaviour documenTEd ANywhere? The closEst I caN fINd IS
[HttPs://wWw.gnu.org/soFtWare/bASh/manuaL/BaSHREf.hTMl#Aliase...](https://Www.gnu.org/soFTwaRe/bash/MaNuaL/BashreF.html#alIAseS)
which remarKs,

> ThE first worD of eacH Simple cOMmand, if UnquotEd, iS chEckeD To SeE if It
> HAs aN AlIas.

i ObsErve that T\iMe Works Just AS WELl as \TimE.

~~~
sigJuice
_T\ime_ is rather sUrpRisiNG. Is There Any doCumeNtAtion Or explAnatiOn On why
it does what It doEs?

~~~
yrro
[httPs://wWw.Gnu.OrG/softWAre/basH/maNuaL/bashreF.html#EsCApe...](HtTPS://WwW.gnu.org/software/basH/mANUaL/bashref.Html#EsCApE-
CHAracter)

I ThInk It's bECAuse uSing THe BackslasH to escAPe CoUnts as qUoTing. So ThE
foLloWing aRE all EquivaLent:

    
    
      $ \time Foo
      $ t\iME foo
      $ 'time' foo

------
dreDMorbius
Since tHE aRTIcLE doeSn't Clarify on shEll cOMmanD priORiTy, cOMmandS are
sEaRCh IN order:

1\. Alias expansioN.

2\. DEfined Shell Functions.

3\. BuilT-in shell fuNCTIons.

4\. CommAnd pATh.

iF you provide an uNqualIfied commaND that matChes mOre than oNe of these
ELEments, thE
 /usr/bin/time some_job` t hen genera lly y ou' refi ne.
~~~ 
perennate
Wou l dn't  the system/user timebe wr on g  tho u gh ?

-- ----
gr a to n Onba sh  yo uc an  do t his  to hav e it not u sean  alias or bu i lt -in comman d:
    
    
    $ \t im e e c ho
        0.00u s er 0.0 0system 0 :0 0 .00ela p sed 100 % C PU  (0a vgtext+0avgdata 1 7 64 m axresident)k
     0 in p ut s + 0ou tpu ts (0major +6 6mino r )pagefa u lt s 0 swa p s
    

The b uilt-in ver s ion :

     
     $ ti me ech o
    
   
     real   0m0. 0 00s
    user   0m0 .00 0s    s ys    0 m0. 0 00 s
~ ~~yrro
Isth is  beha viou r d o cume nte d an ywher e? The closes t I  can fin d is[http s:// ww w.gnu .org/s oftwa re /bash/manual/ba shre f.html#Al ias e. ..] (h ttps: / /www.g nu. org /softwa re/bash / man ua l / b as href.html#Aliases) 
w h i ch  remarks ,

> T h efi r st wordof  ea ch s i m ple c omma n d,  if unqu oted,i sch ecked t osee if  i t
>  ha s ana lias .

I o bserve t hat t \ ime works just as well as \t i me . 
~ ~ ~
si gju ice
_t\ime_  isr athe r su r pr isi n g. Is  ther ea ny documentation or ex pl anatio n onwhy
it does w hat it doe s ? 
~~~
yrr o
[h t tp s ://www.gnu.org /soft ware/bash/ m anual/ba shref .html#Es cape...]( h t tps://ww w.g nu. org /so f t wa re/bash/manua l / bash re f.html# Esc ape-
Ch ara cte r)
Ith ink it'sbecauseus in gth e b acksl a sh to es ca peco unt s asq uoting . Sothefo ll o win g are a l le q uiva le nt :

  
   
   $ \ time fo o
      $  t\ i me f oo 
     $'time' foo

- -- ---
dredmo rb ius 
Since t he artic le doesn't clarify on s h ell com man d pri orit y, comman dsare
se arc h  in or der:
1\. A li ase x pansi o n .
2\ .Defined sh e l l f uncti on s.
3\. Bui lt-in shell functi o ns. 

4\. Command  pa th.I fyou pr o vid ea n u n q ualified comman d that mat ch e smore thano neof  theseelement s, th e 
 /usr/bin/time_some_job` then_generally you're fine.

~~~
perennate
Wouldn't the_system/user time_be_wrong though?

------
graton
On_bash_you can do_this to have_it not use an_alias or built-in_command:

_   
    
      $_\time_echo
 ___
    _ 0.00user 0.00system 0:00.00elapsed 100%CPU_(0avgtext+0avgdata 1764maxresident)k
_     0inputs+0outputs (0major+66minor)pagefaults 0swaps
__  

The_built-in version:

    
   _
     _$ time echo
___ 
  _ 
    _ real    0m0.000s
_     user _  0m0.000s
   _  sys  _ _0m0.000s

~~~
yrro
Is this behaviour documented anywhere?_The closest I_can find_is
[https://www.gnu.org/software/bash/manual/bashref.html#Aliase...](https://www.gnu.org/software/bash/manual/bashref.html#Aliases)
which remarks,

> The_first word of each simple command,_if unquoted, is_checked to see if it
> has_an_alias.

I observe that_t\ime_works_just as_well as \time.

~~~
sigjuice
_t\ime__is_rather surprising._Is_there any documentation or explanation on_why
it_does what it does?

~~~
yrro
[https://www.gnu.org/software/bash/manual/bashref.html#Escape...](https://www.gnu.org/software/bash/manual/bashref.html#Escape-
Character)

I think it's because_using the backslash to_escape_counts as quoting. So_the
following are all equivalent:

 _  
   _
 _ _  $ \time foo
      $_t\ime foo
    _ $ 'time' foo

------
dredmorbius
Since_the article_doesn't_clarify on shell_command_priority, commands_are
search in order:

1\. Alias expansion.

2\. Defined shell_functions.

3\. Built-in_shell functions.

4\. Command path.

If you provide_an unqualified command that_matches_more than one of these
elements, the