Zsh Mailing List Archive
Messages sorted by:
Re: segfault on menu-select
- X-seq: zsh-workers 28232
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: segfault on menu-select
- Date: Sun, 05 Sep 2010 21:11:47 -0700
- In-reply-to: <20100831143337.GA1108@xxxxxxxxxx>
- List-help: <mailto:email@example.com>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <87wrrv4yrg.fsf@xxxxxxxxxxxxxxxxxxxxxx> <20100812165307.GA24998@ph> <87r5i34v51.fsf@xxxxxxxxxxxxxxxxxxxxxx> <20100812173356.GC24998@ph> <100812160702.ZM20648@xxxxxxxxxxxxxxxxxxxxxx> <20100813080811.GB495@ph> <100813085709.ZM22377@xxxxxxxxxxxxxxxxxxxxxx> <20100813214357.012f7f35@pws-pc> <100815134326.ZM20936@xxxxxxxxxxxxxxxxxxxxxx> <100815153444.ZM21188@xxxxxxxxxxxxxxxxxxxxxx> <20100831143337.GA1108@xxxxxxxxxx>
On Aug 31, 4:33pm, Philipp Hartwig wrote:
} Subject: Re: segfault on menu-select
} > The difference seems to be whether the zsh/compctl module is loaded. I
} > don't immediately know why zsh/compctl would be necessary for proper
} > execution of menu-select, but if I add
} > zmodload zsh/compctl
} > to the minimal zshrc, I am no longer able to force a crash.
Hmm, and hmm again. (Yes, I'm hmm-ing at my own previous remarks.)
} I also do not experience any more crashes since adding
} zmodload zsh/compctl
} to my .zshrc. Unfortunately this breaks the menu-select feature in some
I've been fooling with this a bit, and it's not broken; the best I can
describe it is to say it's just not ready to start yet.
} [in a directory with files baz-foo and test-foo and compctl not loaded]
} ph% vi foo<tab><tab><ctrl-o>
} will work out nice and give me the desired menu-selection (or crash).
} But if I [zmodload zsh/compctl as well], no menu-select will
} take place anymore.
I can reproduce this. However, menu-select will take place for me if I
simply add one more TAB:
torch% vi foo<tab><tab><tab><ctrl-o>
This comes down to the code passing through the "else" branch at lines
1013 - 1025 of Src/Zle/compcore.c -- with compctl not loaded, dat.lst
is 0 after runhookdef(COMPCTLMAKEHOOK, ...), but with compctl loaded
dat.list becomes nonzero if we have not made a third attempt to allow
compctl to perform default completion of -foo.
Now, what this has to do with the crash (not) happening after we have
passed (or not) through the compctl hooks, I still don't follow.
Messages sorted by: