[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `
|
From: |
Drew Adams |
|
Subject: |
bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer' |
|
Date: |
Mon, 7 Mar 2011 07:10:03 -0800 |
> I only tried to emulate the current behavior. Usually, at least the
> *scratch* or *Messages* buffer should be around so I suppose that in
> practice it's always possible to kill the current buffer.
Yes, I think so. And that behavior (always kill) will be less confusing to
users, IMO. Keep it simple.
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in calls to `kill-this-buffer', tlh, 2011/03/06
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in calls to `kill-this-buffer', Eli Zaretskii, 2011/03/06
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in calls to `kill-this-buffer', martin rudalics, 2011/03/06
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer', Drew Adams, 2011/03/06
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer', martin rudalics, 2011/03/06
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer', Drew Adams, 2011/03/06
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer', martin rudalics, 2011/03/07
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer',
Drew Adams <=
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer', Johan Bockgård, 2011/03/27
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer', martin rudalics, 2011/03/29
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in calls to `kill-this-buffer', Stefan Monnier, 2011/03/06
- bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in calls to `kill-this-buffer', martin rudalics, 2011/03/07