aboutsummaryrefslogtreecommitdiff
path: root/docs/multi-state-filter-spec.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-05 02:08:43 -0500
committerCraig Jennings <c@cjennings.net>2026-06-05 02:08:43 -0500
commit877c104bfa8497324de45b2fef96dd4520da07e4 (patch)
tree6ddb080df52cada9815a704eea3b4b37981bb2e6 /docs/multi-state-filter-spec.org
parent5940d7caf21f5c2b8e322a67f32657dace56fc9a (diff)
downloadpearl-877c104bfa8497324de45b2fef96dd4520da07e4.tar.gz
pearl-877c104bfa8497324de45b2fef96dd4520da07e4.zip
fix(render): serialize the source header in full regardless of print-length
The #+LINEAR-SOURCE descriptor was written with a bare prin1-to-string, which honors the user's print-length and print-level. A long source, like a Custom View's (it carries a sort vector, a url, and several keys), truncated to "..." for anyone whose config caps those (mine sits at 10). The header then read back as a malformed, odd-length plist, so refresh and the new sort commands errored on the view. A short source like my-open-issues fit under the cap and hid the bug. pearl--linear-source-string binds both to nil around the serialization, and the two header writers (the full render and the sort header rewrite) go through it. I caught it dogfooding the interactive sort live on a real view.
Diffstat (limited to 'docs/multi-state-filter-spec.org')
0 files changed, 0 insertions, 0 deletions