From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Subject: Re: Bug with long multiline strings?
Date: Thu, 25 Oct 2012 11:21:00 +0200 [thread overview]
Message-ID: <87bofqq54z.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20121025095936.621c7717@pws-pc.ntlworld.com> (Peter Stephenson's message of "Thu, 25 Oct 2012 09:59:36 +0100")
Peter Stephenson wrote:
> On Wed, 24 Oct 2012 17:10:23 +0100
> Peter Stephenson <p.stephenson@samsung.com> wrote:
>> Looks like there's a Mystery Ingredient.
>
> The only thing I've been able to think of is that some editor widget is
> running, and it's doing something which isn't saving and restoring the
> lexical state properly. If it's something like that, it wouldn't be too
> hard, if you can see the problem, to rustle up something that checks if
> tokstr/bptr or the heap they're part of are being swept away
> incorrectly. It's not happening on any of my installations.
Yeah, I cannot reproduce the issue from "zsh -f". So there's something
in my setup that helps triggering it. I'll bisect through my
configuration to see what is causing this. But I won't get to it before
Sunday in all likeliness.
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2012-10-25 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 15:21 Frank Terbeck
2012-10-24 16:10 ` Peter Stephenson
2012-10-24 16:31 ` Peter Stephenson
2012-10-25 8:59 ` Peter Stephenson
2012-10-25 9:21 ` Frank Terbeck [this message]
2014-01-17 20:24 ` Frank Terbeck
2014-01-18 21:34 ` Bart Schaefer
2014-01-19 4:59 ` Bart Schaefer
2014-01-19 11:28 ` Frank Terbeck
2014-01-19 12:01 ` Bug reports after releases (was: Re: Bug with long multiline strings?) Axel Beckert
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=87bofqq54z.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--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).