<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pearl/tests/test-pearl-comments.el, branch main</title>
<subtitle>Pearl Edits and Reflects Linear — manage Linear.app issues as org-mode in Emacs
</subtitle>
<id>https://git.cjennings.net/pearl/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/pearl/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/pearl/'/>
<updated>2026-05-24T22:21:29+00:00</updated>
<entry>
<title>feat: make comment sort order configurable, newest-first by default</title>
<updated>2026-05-24T22:21:29+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-24T22:21:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/pearl/commit/?id=cc599d3e9d37c200d49f723ff8e8ce694acd33f8'/>
<id>urn:sha1:cc599d3e9d37c200d49f723ff8e8ce694acd33f8</id>
<content type='text'>
I added pearl-comment-sort-order to choose how an issue's comments render under the Comments heading: newest-first (the default, most recent on top) or oldest-first (chronological, like an email thread). Both the render sort and the add-comment insertion point honor it, so a new comment lands at the top for newest-first and at the bottom for oldest-first.
</content>
</entry>
<entry>
<title>test: cover comment insertion and extraction boundary cases</title>
<updated>2026-05-24T20:24:12+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-24T20:24:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/pearl/commit/?id=11109b45094eaecc1dc87a2e99afab4040732c8f'/>
<id>urn:sha1:11109b45094eaecc1dc87a2e99afab4040732c8f</id>
<content type='text'>
Added ERT tests: append targets the current issue's Comments subtree even when a later issue already has its own Comments; add-comment from inside a comment subtree refuses (no issue id at that heading); edit-current-comment refuses a comment missing LINEAR-COMMENT-ID with no network call; and a comment body containing drawer-looking (:note:) text reads back intact. 380 tests green.
</content>
</entry>
<entry>
<title>feat: pearl — manage Linear issues from org-mode</title>
<updated>2026-05-24T18:44:34+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-24T18:44:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/pearl/commit/?id=b081d62276378b3168c92c06153fd59db0589535'/>
<id>urn:sha1:b081d62276378b3168c92c06153fd59db0589535</id>
<content type='text'>
Pearl fetches Linear issues into an org file and syncs edits back. It covers list / custom views / saved queries, per-issue and bulk rendering with comments inline, conflict-aware sync of descriptions, titles, and comments, field commands for priority / state / assignee / labels, and a transient dispatch menu. The render folds to a scannable outline and nests issues under a sortable parent.

Based on and inspired by Gael Blanchemain's linear-emacs.
</content>
</entry>
</feed>
