From: Philipp Hartwig <ph.hartwig@googlemail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers mailing list <zsh-workers@zsh.org>
Subject: Re: segfault on menu-select
Date: Fri, 13 Aug 2010 10:08:11 +0200 [thread overview]
Message-ID: <20100813080811.GB495@ph> (raw)
In-Reply-To: <100812160702.ZM20648@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
> So I can force my shell through that same branch by hitting ^o in a
> directory containing exactly one file, but I still don't get a crash.
>
> What does "ls" show just before you begin completing?
It's independent of that, it also works in an empty directory as I've
just checked.
Note that in order to reproduce the issue it really seems to be
necessary to have the 4 lines
autoload -Uz compinit
compinit
zmodload -i zsh/complist
bindkey '^o' menu-select
in your .zshrc. Just typing them or sourcing a file containing them will
not lead to the crash in my case, even without the "-f" option. Instead
I get a browsable list of all the files in the directory as it is
supposed to be.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-13 8:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 14:46 Philipp Hartwig
2010-08-12 14:53 ` Frank Terbeck
2010-08-12 15:20 ` Philipp Hartwig
2010-08-12 15:49 ` Frank Terbeck
2010-08-12 16:53 ` Philipp Hartwig
2010-08-12 17:07 ` Frank Terbeck
2010-08-12 17:33 ` Philipp Hartwig
2010-08-12 18:04 ` Frank Terbeck
2010-08-12 23:07 ` Bart Schaefer
2010-08-13 8:08 ` Philipp Hartwig [this message]
2010-08-13 15:57 ` Bart Schaefer
2010-08-13 20:43 ` Peter Stephenson
2010-08-15 20:43 ` Bart Schaefer
2010-08-15 22:34 ` Bart Schaefer
2010-08-31 14:33 ` Philipp Hartwig
2010-09-06 4:11 ` Bart Schaefer
2011-01-09 18:56 ` Philipp Hartwig
2011-01-09 19:54 ` Bart Schaefer
2011-01-09 20:57 ` Philipp Hartwig
2010-08-12 16:04 ` Bart Schaefer
2010-08-12 17:03 ` Philipp Hartwig
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=20100813080811.GB495@ph \
--to=ph.hartwig@googlemail.com \
--cc=schaefer@brasslantern.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).