|
1 | | -# π€ monitor |
| 1 | +# πΊ `tvmux` |
2 | 2 |
|
3 | 3 | So I want to capture my dev work in tmux so I can train models on how to program |
4 | 4 | and actually use a computer. More data is good. |
5 | 5 |
|
6 | 6 | This is my current tmux setup, including my `tmux.conf`. |
7 | 7 |
|
8 | | -## `0.3.0` |
| 8 | +## `0.3.1` |
9 | 9 |
|
10 | 10 | This shell script records a session following the active pane. After some turd |
11 | 11 | polish and more testing, I plan to expand it to work with one window per |
12 | | -project and separate recordings for each. I'll likely split it up into a library |
13 | | -of bash scripts that are concatenated on deployment, like I have in |
14 | | -[π rip](https://github.com/bitplane/rip). |
15 | | - |
16 | | -From 0.3 onwards, with each stable period I'll tag it as a "release" even though |
17 | | -it's not really a release. |
| 12 | +project, quantizing recordings, asciinema streaming etc etc |
18 | 13 |
|
19 | 14 | ## To-do |
20 | 15 |
|
21 | 16 | ### General |
22 | 17 |
|
23 | | -- [ ] get the monitor panel working so i don't need to manually create it each |
| 18 | +- [ ] get the monitor panel working so I don't need to manually create it each |
24 | 19 | reboot. |
25 | | -- [ ] Write a `./configure` script that checks all the things we need. |
26 | | -- [ ] `make build` and `make install` to `$PREFIX`, defaulting to `~/.local/` |
| 20 | +- [x] Write a `./configure` script that checks all the things we need. |
| 21 | +- [x] `make build` and `make install` to `$PREFIX`, defaulting to `~/.local/` |
27 | 22 |
|
28 | 23 | ### `0.4` |
29 | 24 |
|
30 | 25 | - [ ] Record everything and selectively switch between buffers |
31 | 26 | - [ ] timestamp logs with an awk script |
32 | 27 | - [ ] Get alternative buffers working |
33 | | -- [ ] Break stuff into a library? |
| 28 | +- [x] Break stuff into a library + pack it |
| 29 | +- [ ] quantize because spinners are a menace |
| 30 | + - thought: set a cps limit and send full buffers if exceeded |
34 | 31 |
|
35 | | -### `0.5` |
| 32 | +### `__future__` |
36 | 33 |
|
37 | 34 | - [ ] Command line args / flags / config |
38 | 35 | - [ ] Consider a generic settings approach that works with config file, args |
39 | 36 | and env vars as first class citizens. |
40 | | - - [ ] Consider different entrypoints. |
41 | | -- [ ] Review breaking down into functions like in `rip` |
| 37 | +- [ ] Move deployment/install code into the script itself |
| 38 | + - [ ] Put markers in so it can unpack itself to source π |
| 39 | + - [ ] Think about how to pack docs, unpacking full source with makefile and |
| 40 | + `README.md`? π€― |
0 commit comments