From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: one time in 20 error
Date: Wed, 30 Nov 2022 19:20:29 -0800 [thread overview]
Message-ID: <e35c2f14-abda-93d7-bf2c-6823d6d3215d@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7aW9meLuEKSGsKiZMXoAd7KBc9fgakXZnB_t2iphq=BPQ@mail.gmail.com>
On 2022-11-30 16:03, Bart Schaefer wrote:
> but there's nothing else to distinguish
> that from something that was typed on the keyboard, it's all on the
> same stream.
I understand. I know it's complicated. Still one should be able to
choose to dump whatever buffer might have some pending stream. But as I
said, the 'timeout' seems to do exactly that. It's quite functional,
the rest is curiosity at this point ... like why I never see 'RELEASE'.
It has to happen, so I'll figure out why I can't see it.
> This has ceased to be a zsh question and become a curses question.
I don't know how much of zcurses is different from whatever it descends from, but it seems to be within scope as a question. Nevermind tho, if anyone's interested that's fine, if not, I'm functional.
next prev parent reply other threads:[~2022-12-01 3:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:40 Ray Andrews
2022-11-28 17:54 ` Roman Perepelitsa
2022-11-28 20:34 ` Ray Andrews
2022-11-28 20:46 ` Roman Perepelitsa
2022-11-28 22:16 ` Ray Andrews
2022-11-28 22:24 ` Roman Perepelitsa
2022-11-28 23:18 ` Ray Andrews
2022-11-29 2:48 ` Risto Laitinen
2022-11-29 3:27 ` Ray Andrews
2022-11-29 10:13 ` Roman Perepelitsa
2022-11-29 13:29 ` Ray Andrews
2022-11-30 4:32 ` Bart Schaefer
2022-11-30 13:56 ` Ray Andrews
2022-11-30 14:10 ` Roman Perepelitsa
2022-11-30 20:23 ` Ray Andrews
2022-11-30 23:17 ` Ray Andrews
2022-11-30 23:46 ` Bart Schaefer
2022-12-01 0:03 ` Bart Schaefer
2022-12-01 3:20 ` Ray Andrews [this message]
2022-12-01 9:19 ` Roman Perepelitsa
2022-12-01 14:35 ` Ray Andrews
2022-12-01 14:42 ` Philippe Altherr
2022-12-01 21:19 ` Ray Andrews
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=e35c2f14-abda-93d7-bf2c-6823d6d3215d@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).