This is some kind of a follow up on "Segfault on recursive trap/kill"
reported by Mike Grewitz.
After setting FUNCNEST and the listing a file or using 'vi filname[TAB]' a
bug is triggered.
This is how I could reproduce this:
f3d0r4:~/FOO# FUNCNEST=4
f3d0r4:~/FOO# ls
procps-ng-3.3.12-3.fc28.src
On Okt 08 2018, Valentin Bajrami wrote:
> This is some kind of a follow up on "Segfault on recursive trap/kill"
> reported by Mike Grewitz.
>
> After setting FUNCNEST and the listing a file or using 'vi filname[TAB]' a
> bug is triggered.
>
> This is how I could reproduce this:
>
> f3d0r4:~/FOO#
On 10/8/18 8:06 AM, Valentin Bajrami wrote:
> This is some kind of a follow up on "Segfault on recursive trap/kill"
> reported by Mike Grewitz.
>
> After setting FUNCNEST and the listing a file or using 'vi filname[TAB]' a
> bug is triggered.
It's not a bug. FUNCNEST is working as designed. As a
On Mon, Oct 08, 2018 at 02:06:39PM +0200, Valentin Bajrami wrote:
> This is how I could reproduce this:
>
> f3d0r4:~/FOO# FUNCNEST=4
4 is ridiculously low. Set it higher.
On 10/6/18 4:23 PM, Bob Proulx wrote:
> Jeffrey Walton wrote:
>> I think a useful feature for Bash would be to automatically update the
>> program cache after an install.
>
> Put this in your ~/.bashrc file and I believe your use case will be
> much happier.
>
> shopt -s checkhash
How many ins
Chet Ramey wrote:
> Bob Proulx wrote:
> > Put this in your ~/.bashrc file and I believe your use case will be
> > much happier.
> >
> > shopt -s checkhash
>
> How many installers put a new version of an existing package into a
> possibly-different directory with a different name? Even using a s
Mike Gerwitz wrote:
> Bob Proulx wrote:
> > Let me give the discussion this way and I think you will be
> > convinced. :-)
>
> Well, thanks for taking the time for such a long reply. :)
>
> > How is your example any different from a C program? Or Perl, Python,
> > Ruby, and so forth? All of tho
On Mon, Oct 08, 2018 at 11:59:53 -0600, Bob Proulx wrote:
> Some of those must be maintaining the stack in program data space
> instead of in the machine stack space. (shrug)
Indeed. But as I mentioned in another comment, such an implementation
detail shouldn't matter to the user IMO.
> My inte
