Let you save a chat transcript without losing the live session#192
Merged
Let you save a chat transcript without losing the live session#192
Conversation
Saving a chat buffer with C-x C-w or C-x C-s ought to do the obvious thing: write a Markdown transcript to disk. It should not silently retarget the live pi session, confuse toggle or resume, or make Emacs forget which chat buffer belongs to which conversation. This change makes transcript saving behave that way. A saved chat buffer keeps its chat mode and read-only contract, and the live session continues to belong to its original project or named session. Session lookup now uses stable session identity rather than whatever file the buffer happens to be visiting, so project session discovery, toggle, and related commands keep finding the same conversation after a manual save. The documentation now explains the manual transcript workflow in those user terms, and the tests exercise the behavior directly, including named sessions, project-root sessions saved from subdirectories, and the ordinary write-file and save-buffer flows.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Saving a chat buffer with C-x C-w or C-x C-s ought to do the obvious thing: write a Markdown transcript to disk. It should not silently retarget the live pi session, confuse toggle or resume, or make Emacs forget which chat buffer belongs to which conversation.
This change makes transcript saving behave that way. A saved chat buffer keeps its chat mode and read-only contract, and the live session continues to belong to its original project or named session. Session lookup now uses stable session identity rather than whatever file the buffer happens to be visiting, so project session discovery, toggle, and related commands keep finding the same conversation after a manual save.
The documentation now explains the manual transcript workflow in those user terms, and the tests exercise the behavior directly, including named sessions, project-root sessions saved from subdirectories, and the ordinary write-file and save-buffer flows.
Addresses #185 in part.