Bug#742006: [bash] Incomplete grammar in manual page (compound commands)

2014-03-17 Thread Filipus Klutiero
Package: bash Version: 4.3-2 Severity: normal Tags: upstream X-Debbugs-Cc: bug-bash@gnu.org According to the section Compound Commands of the manual page, a compound command is one of 11 forms listed. However, as explained in the ALIASES section, a function definition ( function name [()] compo

Re: When a hashed pathname is deleted, search PATH

2014-03-17 Thread Reuben Thomas
On 17 March 2014 20:46, Chet Ramey wrote: > Because the execution fails in a child process. You'd be able to fix it > for that process, but would do nothing about the contents of the parent > shell's hash table. > Thanks for the explanation. -- http://rrt.sc3d.org

Re: When a hashed pathname is deleted, search PATH

2014-03-17 Thread Chet Ramey
On 3/17/14 4:38 PM, Reuben Thomas wrote: > On 17 March 2014 20:30, Chet Ramey > wrote: > > On 3/17/14 10:17 AM, Dave Rutherford wrote: > > On Mon, Mar 17, 2014 at 10:12 AM, Chet Ramey > wrote: > >> On 3/15/14 2:44 PM, Reuben

Re: When a hashed pathname is deleted, search PATH

2014-03-17 Thread Reuben Thomas
On 17 March 2014 20:30, Chet Ramey wrote: > On 3/17/14 10:17 AM, Dave Rutherford wrote: > > On Mon, Mar 17, 2014 at 10:12 AM, Chet Ramey > wrote: > >> On 3/15/14 2:44 PM, Reuben Thomas wrote: > >>> On 15 March 2014 18:23, Chet Ramey >>> > wrote: > >>> Is there a down

Re: When a hashed pathname is deleted, search PATH

2014-03-17 Thread Chet Ramey
On 3/17/14 10:17 AM, Dave Rutherford wrote: > On Mon, Mar 17, 2014 at 10:12 AM, Chet Ramey wrote: >> On 3/15/14 2:44 PM, Reuben Thomas wrote: >>> On 15 March 2014 18:23, Chet Ramey >> > wrote: >>> Is there a downside to making checkhash the default? >> >> Only the minor

Re: When a hashed pathname is deleted, search PATH

2014-03-17 Thread Chet Ramey
On 3/17/14 10:19 AM, Reuben Thomas wrote: > Only the minor performance hit it would extract on every command lookup. > > > I don't understand, surely it only has a performance impact when a hashed > file or a directory on PATH is (re)moved? Not exactly, since it requires a check of every ha

Re: When a hashed pathname is deleted, search PATH

2014-03-17 Thread Reuben Thomas
On 17 March 2014 14:12, Chet Ramey wrote: > On 3/15/14 2:44 PM, Reuben Thomas wrote: > > On 15 March 2014 18:23, Chet Ramey > > wrote: > > > > It's not been a problem, really. The existence of the `checkhash' > option > > has been enough. How often do you re

Re: When a hashed pathname is deleted, search PATH

2014-03-17 Thread Dave Rutherford
On Mon, Mar 17, 2014 at 10:12 AM, Chet Ramey wrote: > On 3/15/14 2:44 PM, Reuben Thomas wrote: >> On 15 March 2014 18:23, Chet Ramey > > wrote: >> Is there a downside to making checkhash the default? > > Only the minor performance hit it would extract on every command l

Re: When a hashed pathname is deleted, search PATH

2014-03-17 Thread Chet Ramey
On 3/15/14 2:44 PM, Reuben Thomas wrote: > On 15 March 2014 18:23, Chet Ramey > wrote: > > It's not been a problem, really. The existence of the `checkhash' option > has been enough. How often do you remove binaries in directories in > $PATH? > > > Fairly

Re: odd behavior from overloading the "source" builtin

2014-03-17 Thread Chet Ramey
On 3/16/14 5:17 PM, Doug McIlroy wrote: > Apologies for having sent the wrong message before > > GNU bash, version 4.2.39(1)-release (x86_64-redhat-linux-gnu)[5~ > interprets this shell script differently when bash input comes > from a terminal or when it conmes from a file: > source(){