Re: A possible bug on autocompletion after setting FUNCNEST level
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.
Re: A possible bug on autocompletion after setting FUNCNEST level
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 side effect, you have limited functionality enough that bash-completion can't work. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
Re: A possible bug on autocompletion after setting FUNCNEST level
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# 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, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
