all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Newell <chipschap@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Vexing problem with read-char-exclusive (ELISP)
Date: Thu, 1 Aug 2013 17:40:30 -0700 (PDT)	[thread overview]
Message-ID: <2ab66d14-68ef-4f7e-b1ac-e82e4e1df9cc@googlegroups.com> (raw)
In-Reply-To: <mailman.2325.1375377396.12400.help-gnu-emacs@gnu.org>

On Thursday, August 1, 2013 5:03:28 AM UTC-10, Stefan Monnier wrote:
> > I see it with -Q in the current trunk (that is, I see the input echoed

Hmm. Then I won't push forward to 24.x quite yet :)
  
> Hmm... indeed... and I see now also that it's almost "by design".

I can understand that actually being a design choice for some circumstances, however, I think in other circumstances there should be a way to defeat this behavior. (Of course my workaround with a " " prompt seems to do that.)

I'm using read-char-exclusive (to answer an earlier question in this thread) so I can input chars one by one and ignore mouse events. This is part of a typewriter simulator that I posted about on gnu.emacs.sources; it's a relatively useless but somewhat entertaining little piece of code.

But what I think I've heard here is that maybe I should stay with my slightly odd but functional workaround for now.


  parent reply	other threads:[~2013-08-02  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  1:27 Vexing problem with read-char-exclusive (ELISP) Bob Newell
2013-08-01  3:46 ` Stefan Monnier
2013-08-01 10:02   ` Stephen Berman
2013-08-01 15:03     ` Stefan Monnier
     [not found]     ` <mailman.2325.1375377396.12400.help-gnu-emacs@gnu.org>
2013-08-02  0:40       ` Bob Newell [this message]
2013-08-02  2:33         ` Stefan Monnier
     [not found]         ` <mailman.2353.1375410831.12400.help-gnu-emacs@gnu.org>
2013-08-02  3:35           ` Bob Newell
2013-08-02  3:40             ` Stefan Monnier

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=2ab66d14-68ef-4f7e-b1ac-e82e4e1df9cc@googlegroups.com \
    --to=chipschap@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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.