Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: bindkey <whatever> history-beginning-search-backwards; echo $widgts = crash
- X-seq: zsh-workers 23453
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh-Workers <zsh-workers@xxxxxxxxxx>
- Subject: Re: bindkey <whatever> history-beginning-search-backwards; echo $widgts = crash
- Date: Mon, 21 May 2007 22:37:29 -0700
- In-reply-to: <20070522033237.GA4576@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20070521202131.GA14758@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20070522014632.GA11326@xxxxxxxxxxxxxxxxxxxx> <20070522033237.GA4576@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
On May 22, 5:32am, Maddi Kopfermann wrote:
}
} > This is a bug when there is no widget with the supplied name;
}
} Sadly not only in that case!
Why do you think so? In every example you gave, you first bound a key
to a widget that does not exist, and then tried to echo $widgets.
} zsh -fc "bindkey '^o' history-beginning-<TAB> && echo $widgets"
} crashes the shell
}
} the attempt to let completion work crashes the shell.
I don't understand what that example is supposed to be showing. What
do you mean by "let completion work"? Completion only happens in the
line editor in an interactive shell, you can't pass a literal tab to
zsh -fc and expect anything to happen. And even if you mean that you
did type a tab in ZLE, the completion you show would be ambiguous --
ordinarily it would take more than one tab at that position to complete
a valid widget name.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author