Skip to content

Conversation

@robertDurst
Copy link
Contributor

@robertDurst robertDurst commented Sep 9, 2025

Addresses: racket/racket#5224

If a user discovers write-to-file or read-from-file and plans to leverage either without serendipitously also discovering the accompanying editor header/footer methods, they'll likely have a challenging time.

Beyond simply clarifying behavior and linking to header/footer related documentation, also included @alex-hhh 's complete example within the docs for others to discover.


My first contribution. As this is documentation, no accompanying unit-tests or changelog/history updates are required.

Verification

  • raco setup ran successfully
  • docs looked good locally

@racket-discourse-github-bot

This pull request has been mentioned on Racket Discourse. There might be relevant details there:

https://racket.discourse.group/t/how-to-serialize-deserialize-text-editors-and-structures-including-text-editors/3605/8

@mflatt mflatt force-pushed the rdurst/write-to-file branch from 17a97bd to f189c47 Compare January 7, 2026 14:10
@mflatt
Copy link
Member

mflatt commented Jan 7, 2026

Thanks! I updated the branch to avoid a merge conflict and to shift the "See also File Format" to after your explanation.

@mflatt mflatt merged commit cdec779 into racket:master Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants