[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#9310: BadWindow error with quail guidance frame
From: |
Stefan Monnier |
Subject: |
bug#9310: BadWindow error with quail guidance frame |
Date: |
Wed, 17 Aug 2011 09:46:17 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
>> emacs -Q --eval "(setq default-frame-alist '((minibuffer . nil)))" --eval
>> (quail-define-package "Agda" "UTF-8" "A" t)'
>> C-u C-\ agda RET
>> M-%
>>
>> and I get the appended backtrace. As the input method name explains,
>> I bump into this problem when I use Agda (i.e. pretty often these days).
> Is it possible that the frame switched to (0x8c793d8 at #13) is deleted?
AFAIK no frame is deleted in the above scenario, and the frame's
`terminal' field is not NULL (if that's what you were asking).
0x8c793d8 is the minibuffer-only frame.
IIUC your question, you can't reproduce it on your end?
Stefan
- bug#9310: BadWindow error with quail guidance frame, Stefan Monnier, 2011/08/16
- bug#9310: BadWindow error with quail guidance frame, Jan D., 2011/08/17
- bug#9310: BadWindow error with quail guidance frame,
Stefan Monnier <=
- bug#9310: BadWindow error with quail guidance frame, Jan Djärv, 2011/08/17
- bug#9310: BadWindow error with quail guidance frame, Chong Yidong, 2011/08/17
- bug#9310: BadWindow error with quail guidance frame, Stefan Monnier, 2011/08/22
- bug#9310: BadWindow error with quail guidance frame, Jan D., 2011/08/23
- bug#9310: BadWindow error with quail guidance frame, Stefan Monnier, 2011/08/23
- bug#9310: BadWindow error with quail guidance frame, Jan D., 2011/08/24