unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Davin Pearson <davin.pearson@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: read-char bug
Date: Fri, 19 Oct 2018 18:30:38 -0700 (PDT)	[thread overview]
Message-ID: <4e4d0d10-7f2b-49dc-b17c-279b23402b16@googlegroups.com> (raw)

When I run the following code and then press the left mouse button and it goes into an infinite loop.  I have also tried the alternative to read-char, methinks it is something like read-char-exclusive and that fails too.

(let (done ch)
  (setq done nil)
  (when (not done)
  (condition-case err
     (setq ch (read-char "Enter y, n, ! or q"))'
     (error 
        (message "Wrong char")))
        ))
   ch)


             reply	other threads:[~2018-10-20  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20  1:30 Davin Pearson [this message]
2018-10-20  6:31 ` read-char bug Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4e4d0d10-7f2b-49dc-b17c-279b23402b16@googlegroups.com \
    --to=davin.pearson@gmail.com \
    --cc=help-gnu-emacs@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).