From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: History bug (Re: Completion debugging)
Date: Thu, 4 May 2000 17:34:29 +0200 (MET DST) [thread overview]
Message-ID: <200005041534.RAA12349@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Sven Wischnowsky's message of Thu, 4 May 2000 13:40:01 +0200 (MET DST)
I wrote:
> Bart Schaefer wrote:
>
> ...
>
> >
> > So there are still two 113s in the history list, but the prompt has the
> > right history number. I'm expecting that particular shell to crash any
> > time now ...
>
> I get a SEGV reproducibly after C-p C-n. If I take out my patch for
> this, I get it after the C-p.
>
> Hm, maybe someone more knowledgeable with history stuff...?
After playing some more and a couple of SEGVs later...
There is so much mucking around curhist (and histline) in zle that I
wonder if there is a clean way (other than changing the meaning of
curhist in the core and then adapting zle).
Maybe we should just make `print -s' put the strings added while zle
is active into some list and then add those strings only after zle is
left? I.e. in a toplevel-loop() or somewhere around that.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-05-04 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 15:34 Sven Wischnowsky [this message]
2000-05-04 17:39 ` Bart Schaefer
2000-05-04 20:55 ` Wayne Davison
2000-05-05 7:25 ` PATCH: History bug with "print -s" Wayne Davison
-- strict thread matches above, loose matches on Subject: below --
2000-05-04 11:40 PATCH: Re: History bug (Re: Completion debugging) Sven Wischnowsky
2000-05-03 7:07 Sven Wischnowsky
2000-05-03 16:57 ` 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=200005041534.RAA12349@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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).