G'day,
> I see that when you close a buffer, focus goes to the buffer which
> was active before the ex-buffer was selected. I think I would
> prefer to go always to the buffer to the right of the buffer which
> I'm killing.
> ...
I use the code below, which behaves rather like C-w in firefox. I
find it convenient when I have opened a number of links from one page
in buffers in the background.
It's not quite satisfactory though. It might be nice to have a more
sophisticated system where follow-new-buffer-background marks the
parent/child relationship between buffers, based on from where a link
was followed. Then the kill command can go to the next sibling, or up
to the parent.
--8<--
/** Convenient for reading series of opened buffers. */
interactive("kill-and-next-buffer",
"Kill the current buffer and switch to the logical next.",
function (I) {
var bufs = I.window.buffers;
var i = bufs.selected_index;
kill_buffer(I.buffer);
// mozilla behaviour: if (i == bufs.count) i--;
if (i < bufs.count)
bufs.current = bufs.get_buffer(i);});
define_key(content_buffer_normal_keymap, "w", "kill-and-next-buffer");
-->8--
regards, David (with apologies for the obnoxious disclaimer)
--
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the
CRIMES ACT 1914. If you have received this email in error, you are
requested to contact the sender and delete the email.
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror
