The other option, less intrusive, would be to send the killed tabs in reverse order, but it'd seems strange when looking at the session file otherwise. So, add a `append' flag to kill_tab to optionally append the killed tab instead of pre-pending it.

Save closed tabs to a "killed tabs" queue, for up to a max of "max-killed-tabs", and allow to re-open them. Keep the tab history but not its content. This integrates nicely with the session file, just add the "killed" flag as alias for TAB_KILLED and put it in the ktabshead queue upon initalization. It's thus possible to re-open closed tabs even after telescope has been closed, and tabs keeps their history! Add a new cmd, cmd_tab_undo_close, to try to re-open the most recently closed tab and bind it to `u'. While here, add a TODO for the tab history memory leak.

On RET, execute the command on the selected line rather than what the user typed. This saves a TAB (to expand the entry) and is more in line with the other completion commands.

Now that all the queues are correctly initialised, there's no need for that dance.

this allows cmd_push_button_new_tab to open the new tab right *after* the current one, instead that always at the end.

the reload command doesn't push the current url to the history anymore.