zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: one time in 20 error
Date: Wed, 30 Nov 2022 05:56:03 -0800	[thread overview]
Message-ID: <57e8e248-bb1a-663a-8557-e3fc13f671d4@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7aeERdOcpPzTmKVQFK7HLduh2s1J9VFzumCh6W0SJFqpg@mail.gmail.com>


On 2022-11-29 20:32, Bart Schaefer wrote:
> perhaps 'zcurses
>> end' should take more care to clean up?
> I suspect that your program is taking action on mouse-down, so it
> really is up to you to also handle the following mouse-up.
I'm capturing both PRESSED and CLICKED, the former being a slow click in 
practice.  I had the same idea tho, the mouse-up is dangling.  What's 
puzzling is that I can't force the error.  I can press and hold the 
button, wait for the program to end (so far mouse clicks always make a 
selection from a list and return) and then release the button and, 
again, maybe one time in 20 I'll get the bogey.  I've tried variation on 
click speed but nothing  makes it better or worse.   You don't suppose 
it could be a mechanical issue with the mouse?  You know how they 
sometimes get sticky and mouse clicks are poorly registered?  I've had 
mice that tended to return two clicks when only one was made.  A 
mechanically unclean release seems to confuse the computer.
> There's no
> way for curses endwin() or by extension "zcurses end" to know that the
> extra characters were generated by the terminal or were typed by you
> (with the expectation that they'd go to the regular shell input).

Well, so far the 'timeout' is working 100%, still I myself would sorta 
build that in to 'zcurses end'.  While in zcurses,it owns all inputs so 
on quitting the idea that some input would be 'forwarded' to the 
terminal seems strange.  Dunno, maybe such a thing could be wanted but 
... well, could it ever be wanted?  As you say there are these 
'generated by the terminal' ... but I don't know anything about such 
things.  Seems to me the terminal receives input, not makes input but I 
suppose an xterm is itself a program that writes to hardware so ... But 
this is the only time I've ever seen ghost-writing to zle.

BTW you were right about ERR_EXIT, sheesh, it nukes the whole terminal.  
I had something like ERR_RETURN in  mind but I guess we don't have that.





  reply	other threads:[~2022-11-30 13:57 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 [this message]
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
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=57e8e248-bb1a-663a-8557-e3fc13f671d4@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).