Commits
- Commit:
23ca9d13ca4a4a1ef66bd6fa717bef548dbe8fba
- From:
- Omar Polo <op@omarpolo.com>
- Date:
meeeeuhteuhethuet
- Commit:
e39aa21224e2dc8acb8385118b4b17f99f2ccb7e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
kill old, unused forward prototype for non-existant struct page
- Commit:
6fed00b04fadcd9bccf5671e72749512d6ac0d05
- From:
- Omar Polo <op@omarpolo.com>
- Date:
modeline: add an extra - after the trust status char
in part for symmetry, and in part because it seems a good spot to
add an indicator for the presence of a client certificate in the
future.
- Commit:
d18cfb58c93397b6e3de32bd469d52a766a65bfa
- From:
- Omar Polo <op@omarpolo.com>
- Date:
specify that --help and --version also exit
- Commit:
1d8d557f901e618811f03ddb799ebf7cad34227a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
remove the description about the session file format
It's been changed recently (see history & killed files) and I don't
want to keep documenting it: users shouldn't mess with their history
file that easily (this is not an excuse for sloppy parsing, which
isn't the case.) Furthermore, the format is easy, I think intuitive,
and the code easily found in fs.c.
- Commit:
05de8ac36a0646bbcf74d36b25b96244ac1290ff
- From:
- Omar Polo <op@omarpolo.com>
- Date:
append killed tabs when parsing session to preserve the order
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.
- Commit:
d2b2612ba9fbd6549248a3bb347f15672b2c7915
- From:
- Omar Polo <op@omarpolo.com>
- Date:
bump manpage date
- Commit:
1b45e5df963885e127b251dbb6d8f6d5e704cf47
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix outdated comment
free_tab now operates exclusively on the killed tabs list, so don't
mention the current_tab.
- Commit:
265508d0c8d4d558a8661b9cd5936317f72a1c79
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add double space at the end of the sentence
- Commit:
eae77727b91ee9f0c2dc02efb013093b6dadd387
- From:
- Omar Polo <op@omarpolo.com>
- Date:
unroll recursion
- Commit:
39b13ff711838acc339b6d915caabdc63e9b81fb
- From:
- Omar Polo <op@omarpolo.com>
- Date:
decrement the length in hist_clear_forward
- Commit:
bf935370ba5b03432f48ab4d05d6dc74416a85a6
- From:
- Omar Polo <op@omarpolo.com>
- Date:
plug history memory leak
when freeing a tab we have to release also its history.
- Commit:
91091d0c07baa6a064e8aff36e57139b397cf82a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add a maximum (undocumented) value as safety net
- Commit:
4e5935f4e097b5103da46c2ca6b50b437b99cabe
- From:
- Omar Polo <op@omarpolo.com>
- Date:
document max-killed-tabs and tab-undo-close
- Commit:
6c74799d01bfb8706f1972917da936fc2eee66da
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow to re-open closed tabs
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.