Re: [patch] edit-utils: ibuffer.el - make it default
"Stephen J. Turnbull" <stephen(a)xemacs.org> wrote:
>>>>> "jpw" == John Paul Wallington
<jpw(a)shootybangbang.com> writes:
jpw> Moving ibuffer.el out of packages and into core lisp is
jpw> better for a future XEmacs, but then deprives existing
jpw> XEmacsen. Hmm.
If ibuffer.el doesn't use any non-public APIs, move it to xemacs-base,
and the existing file in core can go away in future versions.
I think this is a good idea. However, before buff-menu can disappear
popular entry points would probably have to be replicated; ibuffer
isn't (yet) a drop-in replacement.
Whilst I would strongly prefer that C-x C-b and Buffers > List All
Buffers use ibuffer by default (without any user customizations),
I think a packageless XEmacs should use the old list-buffers rather
than bag-out.
Then dump xemacs-base at build-time.
This sounds intriguing...
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?
--
John Paul Wallington