Josh Glover writes:
On 20/03/2008, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
> How did you invoke `revert-buffer'? Through a menu as the backtrace
> would tend to suggest?
Yes. My system was under a reasonably heavy load at the time (emerging
qt4 and Amarok), but not such a heavy load that reverting should have
taken two minutes, so I think XEmacs was in fact wedged.
Probably. As I say, problems with modal dialogs are known to occur.
I hate that code (it was written very much with Windows in mind, where
modal dialogs are the rule, not X, where modal dialogs are generally
discouraged), so I haven't studied it much (or I'd fix it, probably
with something like C-u C-u C-u C-u C-u C-k ;-).
The other possibility is some kind of crash due to the progress bar.
I assume that SIGINT triggered the backtrace, right?
Yes. Any abnormal termination should generate a backtrace.
I know this is not the venue, but while I have your attention, is
there a keybinding for revert-buffer?
Not by default. The way to find bindings is C-h w revert-buffer RET.
On a GUI, you can use menu accelerators: Alt f r.
Of course you can interactively make a binding with `local-set-key'
(specific to current mode) or `global-set-key' (in global map).
`define-key' is the recommended interface for code including init.el.
It is recommended that you use C-c <letter> combinations for local
bindings, as those are reserved for users. Even function keys are
coopted by some modes.
XEmacs-Beta mailing list