* Interrupt causing problems for subsequent completions
@ 2000-06-09 5:42 Felix Rosencrantz
0 siblings, 0 replies; 2+ messages in thread
From: Felix Rosencrantz @ 2000-06-09 5:42 UTC (permalink / raw)
To: zsh-workers
>> 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.
-FR.
__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Interrupt causing problems for subsequent completions
@ 2000-06-09 7:25 Sven Wischnowsky
0 siblings, 0 replies; 2+ messages in thread
From: Sven Wischnowsky @ 2000-06-09 7:25 UTC (permalink / raw)
To: zsh-workers
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-06-09 7:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-06-09 5:42 Interrupt causing problems for subsequent completions Felix Rosencrantz
2000-06-09 7:25 Sven Wischnowsky
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).