John Paul Wallington <jpw(a)shootybangbang.com> wrote:
For me, the important question is: should C-x C-b and/or the Buffers
>
List All buffers menu item use ibuffer? If so, just for new XEmacsen
or retrospectively too?
Personally, I think they should use ibuffer. I still like the idea of
applying these defaults retrospectively via the package-system time
machine, but it may piss some people off.
Would "it's easy to revert to the old behaviour: just customize
ibuffer-substitute-list-buffers-key-definition (no need to restart
XEmacs even), or set it to nil in your init-file" placate them?
Idiot. Because of the :set keyword it ain't setq-able. So the
answer would instead be: "umm. You have to customize it. No, setq
will not do." Which would not placate them.
So changing core is probably better. I just did this:
--- lisp/menubar-items.el.orig Thu Jan 31 16:26:26 2002
+++ lisp/menubar-items.el Thu Jan 31 16:30:44 2002
@@ -1442,7 +1442,7 @@
["Go To %_Previous Buffer" switch-to-other-buffer]
["Go To %_Buffer..." switch-to-buffer]
"----"
- ["%_List All Buffers" list-buffers]
+ ["%_List All Buffers" (if (fboundp 'ibuffer) (ibuffer)
(list-buffers))]
["%_Delete Buffer" kill-this-buffer
:suffix (if put-buffer-names-in-file-menu (buffer-name) "")]
"----"
And of course it works fine but C-h k (click on the menu item) prints:
misc-user runs (if (fboundp (quote ibuffer)) (ibuffer) (list-buffers))
`if' is a built-in function...
Ha-ha. Is it reasonable to just replace list-buffers in the menu
with ibuffer? Should there be a list-all-buffers wrapper function
with (if (fboundp 'ibuffer) (ibuffer) (list-buffers)) in it?
--
John Paul Wallington