From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Interrupt causing problems for subsequent completions
Date: Fri, 9 Jun 2000 09:25:51 +0200 (MET DST) [thread overview]
Message-ID: <200006090725.JAA22138@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Felix Rosencrantz's message of Thu, 8 Jun 2000 22:42:12 -0700 (PDT)
Felix Rosencrantz wrote:
> >> Also, on a side note, I think there might be a bug in compadd (possibly
> >> matching) that causes it to get in a bad state if an interrupt is sent while
> it
> >> is working. I typically want to interrupt in situations when completion is
> >> slow. Completion works, but matching seems to have some problems. (I know,
> >> you probably want some those helpful details...)
> >
> >Indeed, I do.
>
> Thought so... Sigh, don't have much in the way of details yet. I did notice
> that the signal was being caught by a stack trace that ends like:
>
> strlen
> modify [subst.c:2001]
> paramsubst [subst.c:1538]
> stringsubst [subst.c:121]
> prefork [subst.c:70]
> execcmd [exec.c:1715]
>
> So it looks like compadd is not being interrupted. But maybe the completion
> widget state is somehow messed up.
>
> I have directory /drive2/tools that I attempt to type as "cd /d2/to<TAB>" that
> completes properly ( my matching spec has "r:[^0-9]||[0-9]=**"). But after
> interrupting a completion widget, normal completion fails, and it attempts to
> do correction, and doesn't expand properly.
Yes, sounds more like some of the shell-code state not being reset
properly, I'll have a look (it may well be that this is a pure
shell-code problem, we don't catch SIGINT in there either).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-09 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-09 7:25 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-09 5:42 Felix Rosencrantz
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=200006090725.JAA22138@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).