Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14699 > unrolled thread

Re: A possible bug on autocompletion after setting FUNCNEST level

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: A possible bug on autocompletion after setting FUNCNEST level Andreas Schwab <schwab@suse.de> - 2018-10-08 14:15 +0200

#14699 — Re: A possible bug on autocompletion after setting FUNCNEST level

On Okt 08 2018, Valentin Bajrami <valentin.bajrami@gmail.com> 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# FUNCNEST=4
>
> f3d0r4:~/FOO# ls
> procps-ng-3.3.12-3.fc28.src.rpm
> procps-ng-3.3.12-pmap-all-lines-twice.patch  procps-ng-3.3.12.tar.xz
> procps-ng-3.3.14-CVE-2018-1124.patch  procps-ng.spec  README.md  README.top
>
> f3d0r4:~/FOO# vi pr-bash: __reassemble_comp_words_by_ref: maximum function
> nesting level exceeded (4)

In which way is this a bug?  AFAICT, FUNCNEST is doing its job.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web