Michael Bolin
970e2cba4d
feat: record messages from user in ~/.codex/history.jsonl
2025-05-15 12:32:41 -07:00
Michael Bolin
5d3aef3799
Merge 8b5de5a4d6 into sapling-pr-archive-bolinfest
2025-05-15 09:00:50 -07:00
Michael Bolin
8b5de5a4d6
feat: record messages from user in ~/.codex/history.jsonl
2025-05-15 09:00:47 -07:00
Michael Bolin
b47d24157c
merge commit for archive created by Sapling
2025-05-15 08:59:48 -07:00
Michael Bolin
d7aa41a47e
feat: record messages from user in ~/.codex/history.jsonl
2025-05-15 08:59:44 -07:00
Michael Bolin
910c594882
merge commit for archive created by Sapling
2025-05-15 08:57:18 -07:00
Michael Bolin
558eb03476
feat: record messages from user in ~/.codex/history.jsonl
2025-05-15 08:57:12 -07:00
Michael Bolin
5fc9fc3e3e
chore: expose codex_home via Config ( #941 )
2025-05-15 00:30:13 -07:00
Michael Bolin
96f8c9c052
Merge 1226998d2b into sapling-pr-archive-bolinfest
2025-05-14 23:59:37 -07:00
Michael Bolin
1226998d2b
chore: expose codex_home via Config
2025-05-14 23:59:33 -07:00
Michael Bolin
653177c618
Merge 401af38955 into sapling-pr-archive-bolinfest
2025-05-14 23:58:14 -07:00
Michael Bolin
401af38955
chore: expose codex_home via Config
2025-05-14 23:58:10 -07:00
Michael Bolin
454f63d6f0
Merge 04f9918c3e into sapling-pr-archive-bolinfest
2025-05-14 23:57:19 -07:00
Michael Bolin
04f9918c3e
chore: expose codex_home via Config
2025-05-14 23:57:16 -07:00
Michael Bolin
72109de30d
merge commit for archive created by Sapling
2025-05-14 23:56:35 -07:00
Michael Bolin
cf63787d9a
chore: expose codex_home via Config
2025-05-14 23:56:30 -07:00
Michael Bolin
9f4eba52fb
merge commit for archive created by Sapling
2025-05-14 23:53:10 -07:00
Michael Bolin
499d7e1443
chore: expose codex_home via Config
2025-05-14 23:53:04 -07:00
Michael Bolin
5c65b7364f
Merge f38b3b31eb into sapling-pr-archive-bolinfest
2025-05-14 23:51:28 -07:00
Michael Bolin
f38b3b31eb
chore: expose codex_home via Config
2025-05-14 23:51:24 -07:00
Michael Bolin
93eaf02fae
merge commit for archive created by Sapling
2025-05-14 23:51:16 -07:00
Michael Bolin
5fb7d700e9
chore: expose codex_home via Config
2025-05-14 23:51:09 -07:00
Michael Bolin
e7666e0af9
merge commit for archive created by Sapling
2025-05-14 23:11:35 -07:00
Michael Bolin
09c93d5453
chore: expose codex_home via Config
2025-05-14 23:11:25 -07:00
Michael Bolin
48781cbfe4
merge commit for archive created by Sapling
2025-05-14 22:14:33 -07:00
Michael Bolin
e93540a32a
chore: expose codex_home via Config
2025-05-14 22:14:28 -07:00
Michael Bolin
bbca9be417
merge commit for archive created by Sapling
2025-05-14 22:02:27 -07:00
Michael Bolin
da6fb2842c
chore: expose codex_home via Config
2025-05-14 22:02:23 -07:00
Michael Bolin
0019079e45
Merge a238877fcc into sapling-pr-archive-bolinfest
2025-05-14 22:01:20 -07:00
Michael Bolin
a238877fcc
chore: expose codex_home via Config
2025-05-14 22:00:46 -07:00
Michael Bolin
2beab253ec
Merge 623eec23c4 into sapling-pr-archive-bolinfest
2025-05-14 18:03:31 -07:00
Michael Bolin
623eec23c4
feat: record messages from user in ~/.codex/history.jsonl
2025-05-14 18:02:07 -07:00
Michael Bolin
0b9ef93da5
fix: properly wrap lines in the Rust TUI ( #937 )
...
As discussed on
699ec5a87f (commitcomment-156776835) ,
to properly support scrolling long content in Ratatui for a sequence of
cells, we need to:
* take the `Vec<Line>` for each cell
* using the wrapping logic we want to use at render time, compute the
_effective line count_ using `Paragraph::line_count()` (see
`wrapped_line_count_for_cell()` in this PR)
* sum up the effective line count to compute the height of the area
being scrolled
* given a `scroll_position: usize`, index into the list of "effective
lines" and accumulate the appropriate `Vec<Line>` for the cells that
should be displayed
* take that `Vec<Line>` to create a `Paragraph` and use the same
line-wrapping policy that was used in `wrapped_line_count_for_cell()`
* display the resulting `Paragraph` and use the accounting to display a
scrollbar with the appropriate thumb size and offset without having to
render the `Vec<Line>` for the full history
With this change, lines wrap as I expect and everything appears to
redraw correctly as I resize my terminal!
codex-rs-cb19037ca3822e9b19b51417392f8afc046be607-1-rust-v0.0.2505141652
2025-05-14 16:51:41 -07:00
Michael Bolin
60e16f4c88
merge commit for archive created by Sapling
2025-05-14 16:33:01 -07:00
Michael Bolin
90b2852e40
fix: wrap lines in the TUI
2025-05-14 16:32:56 -07:00
Michael Bolin
f74680305f
merge commit for archive created by Sapling
2025-05-14 16:22:04 -07:00
Michael Bolin
d423414fda
fix: wrap lines in the TUI
2025-05-14 16:21:59 -07:00
Michael Bolin
61a86215ed
merge commit for archive created by Sapling
2025-05-14 16:09:52 -07:00
Michael Bolin
c864c95e68
fix: wrap lines in the TUI
2025-05-14 16:09:46 -07:00
Michael Bolin
b333996afa
merge commit for archive created by Sapling
2025-05-14 15:53:32 -07:00
Michael Bolin
798da3b257
fix: wrap lines in the TUI
2025-05-14 15:53:27 -07:00
Michael Bolin
95db224292
merge commit for archive created by Sapling
2025-05-14 15:46:01 -07:00
Michael Bolin
f09d714d79
fix: wrap lines in the TUI
2025-05-14 15:45:56 -07:00
Michael Bolin
4be52164c4
merge commit for archive created by Sapling
2025-05-14 15:42:19 -07:00
Michael Bolin
f221a9c077
fix: wrap lines in the TUI
2025-05-14 15:42:12 -07:00
Michael Bolin
6139fa2912
merge commit for archive created by Sapling
2025-05-14 15:21:57 -07:00
Michael Bolin
341f143f5b
fix: wrap lines in the TUI
2025-05-14 15:21:52 -07:00
Michael Bolin
38214bf6ec
Merge 8b37e89317 into sapling-pr-archive-bolinfest
2025-05-14 15:20:35 -07:00
Michael Bolin
8b37e89317
fix: wrap lines in the TUI
2025-05-14 15:20:25 -07:00
Michael Bolin
34aa1991f1
chore: handle all cases for EventMsg ( #936 )
...
For now, this removes the `#[non_exhaustive]` directive on `EventMsg` so
that we are forced to handle all `EventMsg` by default. (We may revisit
this if/when we publish `core/` as a `lib` crate.) For now, it is
helpful to have this as a forcing function because we have effectively
two UIs (`tui` and `exec`) and usually when we add a new variant to
`EventMsg`, we want to be sure that we update both.
codex-rs-3a70a0bc280734d09448cb08ec05b5c44f7c798e-1-rust-v0.0.2505141337
2025-05-14 13:36:43 -07:00