emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: `y-or-n-p' does not wait for input - assumes `n'


From: Drew Adams
Subject: RE: `y-or-n-p' does not wait for input - assumes `n'
Date: Sun, 23 Jan 2005 17:49:24 -0800

       However, I just tried the code again, with the same result (bug),
       in vanilla Emacs (-q).

    Just to make sure: and with current CVS?

No, as I said, "I'm using a CVS binary from July - I can't build Emacs
here." I just checked again with my (July) version, to make sure I didn't
make a mistake, and to check about the activation of the menu item that you
mentioned.

       Anyway, Richard tested this with the latest CVS code, and he
       said that it
       works OK (no bug), at least on the platform he used. Thanks
       for checking. -

    It works nearly OK for me too.  That is, I do not see the bug you
    describe.

That's good. The bug is probably fixed in current CVS. Someone might want to
check on Windows (unless you did that), since that is the platform where I
observed the problem.

    But I noticed something else that probably is a bug:

    If you set use-dialog-box to nil

(FYI - I had use-dialog-box = t.)

    and then select "Foo Bar" _with the mouse_,
    "Please answer y or n.  foo: (y or n)" appears in the echo area.
    The "foo: (y or n)" _was_ asked (which you can see by looking at the
    *Messages* buffer), but the mouse click got apparently treated as an
    (invalid) answer to the first "foo: (y or n)" question.

    To debug what goes on in your situation, it could also be useful to do
    `C-h e'.

Yes, I already checked *Messages*. In my case, this is all there is:

 Creating customization buffer...done
 To install your edits, invoke [State] and choose the Set operation
 No

I tried again (in July version), this time with `use-dialog-box' = nil, and
there is no bug - the bug (in my version) is only with `use-dialog-box' = t.
With nil, the question is asked, and the response is treated correctly (and
"foo: (y or n)" appears in *Messages*).

I suspect that the bug is already fixed, but it would be good if someone
could verify on Windows, just to make sure.

Thanks,

  Drew





reply via email to

[Prev in Thread] Current Thread [Next in Thread]