Re: SEGFAULT if bash script make "source" for itself

2014-09-04 Thread bogun.dmitriy
2014-09-03 7:31 GMT-07:00 Chet Ramey : > On 8/28/14, 2:02 PM, bogun.dmit...@gmail.com wrote: > > IMHO any user action should not lead to SIGSEGV! I am not objecting > against > > recursive "sourse" itself. But when I got SIGSEGV from "bash", I have no > > idea why this is happened. I have made rec

RFE: remove duplicate entries from the result of `compgen -W'

2014-09-04 Thread Clark Wang
See following example: $ echo $BASH_VERSION 4.3.18(1)-release $ compgen -W 'hello hello' h hello hello $ It'll be good if only one "hello" is outputted. -clark

Re: "source" cmd creates entry in BASH_SOURCE etc. only if within function

2014-09-04 Thread Chet Ramey
On 9/2/14, 2:59 PM, jim.av...@gmail.com wrote: > Bash Version: 4.3 > Patch Level: 0 > Release Status: release > > Description: > > The "source" (or ".") command, if invoked from within a function, > creates a call frame, setting $FUNCNAME[0] to "source" and > $BASH_SOURCE[1] and $BASH_LINENO[1]

Re: [PATCH] Support configurable mode strings in prompt

2014-09-04 Thread Chet Ramey
On 9/4/14, 7:22 AM, Dylan Cali wrote: > Hi Chet, > > Just curious if it will be possible to merge this enhancement? I haven't looked at it yet. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@

Re: [PATCH] Support configurable mode strings in prompt

2014-09-04 Thread Dylan Cali
Hi Chet, Just curious if it will be possible to merge this enhancement? Thanks, Dylan