Doug Alcorn <lathi(a)seapine.com> writes:
> I have instead used shift-clicking with mouse-3 on the mode-line
> kill the buffer. (Implemented with the help of hyperbole.) This
> gives IMHO greater control and less risk of making a mistake.
Can you post details? I think making a mousable way to kill the
current buffer is a Good Thing; however, you're right that putting it
on the toolbar is a little risky. It's a good idea to put it on the
modeline. Perhaps you're solution should become part of the standard
xemacs distribution (with an option of course).
I don't see why it's so risky. If you're prompted to save the file if
changed you wouldn't loose data. (And the recent-files menu will re-visit
the file again fast.) I wouldn't want to have a self-destruct button on
the toolbar, but a loose-a-few-seconds-if-misclicked button doesn't seem
At any rate, a button like the open button, but with the text "new", that
opened a new buffer not visiting any file would avoid a FAQ.
I can't remember ever using the toolbar, and now that I look at it, it
seems a bit random. The Mail and News buttons for instance, would in my
case only be used once per XEmacs session, which lasts for weeks. To me
toolbars in general is useful for fast access to often used functions (not
having to reach for the keyboard when you're already mousing), and for
seeing the most common operations when first starting to use a program. I
wonder if any "experienced" users use the toolbar at all.
In that spirit, maybe tetris, mine game, calender and rectangle
copy/kill/yank would be worthy of toolbar space. And what about doctor and
flame? Or split-window-vertically, delete-window? What about a button3 pop-up
offering to remove the button, and you could drag a menu option over to the
toolbar to insert an empty icon, right-click on it to set icon and text or
move the button. I guess the problem is finding someone who thinks it's
worth the effort to do it.