Commits
- 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.
- Commit:
83ed72f1b550bd0f43e2950669c15fa09cfc4859
- From:
- Omar Polo <op@omarpolo.com>
- Date:
mark last_time_crashed as static
- Commit:
6c8ddaceb64160cd5a59eae137ee90fce2aa19ee
- From:
- Omar Polo <op@omarpolo.com>
- Date:
s/xdg_init/init_paths/g
- Commit:
7e60a21a63558830da7e7dd476e43e67af348216
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move xdg_* paths as local variables of xdg_init
- Commit:
eb9cbcba6ce8028e674a2b2c59643163bb8e1213
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move session_tab{,_hist} to session.h
- Commit:
6400962be59d6120a4176a7b3e3ea330ebf42669
- From:
- Omar Polo <op@omarpolo.com>
- Date:
mark parse_khost_line as inline
- Commit:
eb722b5028dcd686244ecbca2ff4bfb0a29a6c68
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move know_host parsing to the fs process and load the store via imsgs
Like previously did with the session file, now the main process doesn't
parse anything with the only exception being the configuration file.
With this in, the only bit from fs.h still used in the main process is
the path to the configuration file.
- Commit:
50f036824c2c9c860754f608c478c909642bdab1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
avoid zero-timer hack by triggering session initialization with IMSG_INIT
- Commit:
1040cc7fd1cf748a26766e65b2a2fde17e27310d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
implement persistent tab history
The session file is now overloaded with the history info, that means
that upon startup telescope can repopulate each tab history!
The price to pay is that one can't start an old telescope with a new
session file, otherwise will get a lot of fancy '<' and '>' tabs...
- Commit:
f8c6e75351fd01dc58eabd367348ce79fe131193
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reuse struct session_tab when saving the session
- Commit:
bb28f1c2f6463f1e8881c90bb17a404cf7e5c3b7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move parse_last_session to the fs process
~/.telescope/session was parsed in the main process before dropping in
the sandbox: that's no good. This moves the initialization of the ui
events later in ui_main_loop and makes so that the fs process, after
entering the sandbox, parses and sends the content of the last session
back to the main process; when it's done the ui gets loaded and
telescope is back rocking.
I'm plannig to re-use the struct session_tab during the save session
operation soon.
- Commit:
f88fbabc2b1988a4c36c637b77c842b8f80c9ddb
- From:
- Omar Polo <op@omarpolo.com>
- Date:
adjust some comments text
- Commit:
de04b1788232dab669d2026c101a686199a97c7c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
[xdg] move pages path under $XDG_DATA_HOME instead of CONFIG_HOME
OK andrea
- Commit:
fb3d08c1f0590014fcb4230feb8fda8fa056773e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move declarations from telescope.h in fs.h
and while there also publish various path. It's easier and better to
have all of them exported from here instead of hardcoding them in other
files (such as sandbox.c)
- Commit:
444dad86beaaa60bd96790c7097aa66bb331e645
- From:
- Omar Polo <op@omarpolo.com>
- Date:
dirname fix
dirname(3) is really one of the worst part of POSIX, portability-wise.
Implementors can decide to either modify the passed string or return a
pointer to an internal storage.
The current code fails when dirname returns a pointer to an internal
storage because between the strcmp call and the mkdir we go into a
recursion that can modify `path'. We can't use copy either because
*some* implementation of dirname would have changed that.
How to escape from this hell? Take yet another copy of the path!