From: Eric Cook <llua@gmx.com>
To: zsh-workers@zsh.org
Subject: Re: Segfault when displaying completion lists
Date: Mon, 8 Feb 2016 18:39:14 -0500 [thread overview]
Message-ID: <56B92722.7070004@gmx.com> (raw)
In-Reply-To: <1454972312.10740.8.camel@gladbachcity.de>
On 02/08/2016 05:58 PM, Christian Heinrich wrote:
> Hello,
>
> I'm running ZSH 5.2-3 on my Debian Testing system. This error existed
> previously, too, but I only found the time today to find a minimal
> setup for this. Here we go:
>
> % zsh --norcs
> % zmodload zsh/complist
> % autoload -U compinit && compinit -d ~/.zsh/cache/zcompdump
> % zstyle ':completion:*' list-prompt '%p'
> % bindkey -d
> % ls /usr/lib/<TAB>
> Now a huge list should be displayed with a pager. Press "Arrow Down"
> and it should segfault.
>
>
> This does not happen if the "zsh/complist" module is not loaded.
>
> Another interesting observation:
>
> After the <TAB>, press backspace instead of "arrow down" and remove the
> whole command (do not accept the line). Type "bindkey -d" (yes, a 2nd
> time) and accept. Type "ls /usr/lib/<TAB>" again and press backspace.
> It segfaults now, although backspacing worked the first time.
>
> Maybe someone can find the reason for this? I do have EDITOR="vim" set,
> but it appears as if it happens with EDITOR="emacs" as well.
>
>
> Thanks!
>
> Christian
>
This is a guess:
menu selection requires a keymap named menuselect to function. you can view
it with ''bindkey -l''. This keymap is provided by the complist module
that you loaded initially, then sequentially deleted with ''bindkey -d''
returning the keymaps back to a default state.
The zsh/complist is loaded automatically on first use of menuselect,
which explains why ''zmodload zsh/complist'' is required for the segfault.
If my guess is true, zsh should handle the menuselect keymap not existing more elegantly.
But i wouldn't expect menuselect to be of much use without keybinds.
next prev parent reply other threads:[~2016-02-08 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 22:58 Christian Heinrich
2016-02-08 23:39 ` Eric Cook [this message]
2016-02-09 6:00 ` Bart Schaefer
2016-02-09 10:31 ` Christian Heinrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B92722.7070004@gmx.com \
--to=llua@gmx.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).