From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Proof of concept mainstream plugin manager
Date: Sat, 23 Jan 2016 10:03:56 +0100 [thread overview]
Message-ID: <CAKc7PVCywh3fVsvFOUP3Bi27-8o1w30_E73rs8c+Zd4sOqtT8w@mail.gmail.com> (raw)
In-Reply-To: <160122173705.ZM11491@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On 23 January 2016 at 02:37, Bart Schaefer <schaefer@brasslantern.com> wrote:
> As a final thought, I'd just call this whole thing "zplugin", forget the
> suffix "governor", name the variables ZPLUG_*, etc.
Renamed.
I occur a problem with traps. When zcurses waits for a key and Ctrl-C
is pressed, trap isn't called instantly, but later, in a case. I
attach test source. This is fixed in 5.1 (occurs in 5.0.8), wonder if
I can somehow workaround this:
https://asciinema.org/a/2dnx2ky1q14hna6bvwfrwsvkr
Discouraging, but quite expected. Doing autoload -X is expected to
generate some edge-cases on Zsh usage. If I could test say 30 plugins
from the awesome-zsh-plugins list, and confirm they're all working,
that would be an enabler for autoload -X, otherwise the project's
sense is doubtful.
Best regards,
Sebastian Gniazdowski
[-- Attachment #2: aload --]
[-- Type: application/octet-stream, Size: 448 bytes --]
zmodload zsh/curses
trap "echo Interrupted; return" TERM INT QUIT
zcurses init
zcurses delwin main 2>/dev/null
zcurses addwin main 4 $COLUMNS 0 0
zcurses border main
zcurses refresh main
a() {
b="c"
case "$a" in
x*)
echo "X"
;;
*)
echo "*"
;;
esac
sleep 20
}
# Waits for a key
zcurses input main key keypad
zcurses delwin main
zcurses end
set -x
a
# vim:ft=zsh
next prev parent reply other threads:[~2016-01-23 9:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 19:44 Sebastian Gniazdowski
2016-01-23 1:37 ` Bart Schaefer
2016-01-23 9:03 ` Sebastian Gniazdowski [this message]
2016-01-23 15:54 ` Sebastian Gniazdowski
2016-01-23 16:00 ` Sebastian Gniazdowski
2016-01-23 16:09 ` Sebastian Gniazdowski
2016-01-23 16:26 ` Sebastian Gniazdowski
2016-01-23 17:36 ` Bart Schaefer
2016-01-23 19:20 ` Bart Schaefer
2016-01-23 20:00 ` Bart Schaefer
2016-01-24 10:51 ` Sebastian Gniazdowski
2016-01-24 14:59 ` Sebastian Gniazdowski
2016-01-24 19:06 ` Sebastian Gniazdowski
2016-01-24 20:45 ` Bart Schaefer
2016-06-04 11:36 ` Sebastian Gniazdowski
2016-06-04 17:02 ` Bart Schaefer
2016-01-26 22:50 ` Daniel Shahaf
2016-01-27 7:47 ` Sebastian Gniazdowski
2016-01-26 22:50 ` Daniel Shahaf
2016-01-27 4:34 ` Bart Schaefer
2016-01-27 7:34 ` Sebastian Gniazdowski
2016-01-28 6:38 ` Bart Schaefer
2016-01-28 7:13 ` Sebastian Gniazdowski
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=CAKc7PVCywh3fVsvFOUP3Bi27-8o1w30_E73rs8c+Zd4sOqtT8w@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=schaefer@brasslantern.com \
--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).