From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Crash when capturing command output in completion
Date: Fri, 16 Jan 2015 10:58:14 -0800 [thread overview]
Message-ID: <CAH+w=7amCTv2BewWWrX16Fky2Q6aPYWFU1Sw00Jr=1LBTSN7ZQ@mail.gmail.com> (raw)
In-Reply-To: <20150116180400.6be0d82e@ntlworld.com>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
On Jan 16, 2015 10:09 AM, "Peter Stephenson" <p.w.stephenson@ntlworld.com>
wrote:
>
> On Fri, 16 Jan 2015 08:18:43 -0800
> Bart Schaefer <schaefer@brasslantern.com> wrote:
> > OK, this changed something -- I don't get a crash any more (though I
> > probably should as there is obviously a rogue pointer) but *without*
> > -DZSH_OLD_SKIPCOMM I get this:
> >
> > schaefer<501> echo ÿÿÿÿÿÿÿÿ$(ls)
> > Completing all expansions
> > ÿÿÿÿÿÿÿÿ$(ls)
> > Completing original
> > $(ls)
>
> That's not happening here.
It also does not happen to me when compiling on MacOS, so I will try again
from "make clean" when I am back at my other build machine.
next prev parent reply other threads:[~2015-01-16 18:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 19:34 Vin Shelton
2015-01-15 21:53 ` Bart Schaefer
2015-01-15 23:53 ` Vin Shelton
2015-01-16 0:27 ` Bart Schaefer
2015-01-16 3:11 ` Vin Shelton
2015-01-16 3:17 ` Vin Shelton
2015-01-16 4:43 ` Bart Schaefer
2015-01-16 5:20 ` Bart Schaefer
2015-01-16 9:44 ` Peter Stephenson
2015-01-16 12:57 ` Peter Stephenson
2015-01-16 16:18 ` Bart Schaefer
2015-01-16 16:25 ` Bart Schaefer
2015-01-16 18:04 ` Peter Stephenson
2015-01-16 18:58 ` Bart Schaefer [this message]
2015-01-16 19:16 ` Bart Schaefer
2015-01-16 20:05 ` Peter Stephenson
2015-01-16 19:19 ` Ray Andrews
2015-01-16 6:43 ` Ray Andrews
2015-01-16 7:49 ` Bart Schaefer
2015-01-16 16:21 ` Ray Andrews
2015-01-16 16:34 ` Bart Schaefer
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='CAH+w=7amCTv2BewWWrX16Fky2Q6aPYWFU1Sw00Jr=1LBTSN7ZQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=p.w.stephenson@ntlworld.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).