aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--README.org6
1 files changed, 5 insertions, 1 deletions
diff --git a/README.org b/README.org
index 45798bd..916883c 100644
--- a/README.org
+++ b/README.org
@@ -228,7 +228,11 @@ A *source* is anything Pearl can fetch from: a Linear favorite, a Custom View, a
Pick one and it fetches. List-capable favorites (Custom View / project / cycle / label / user) resolve to the existing filter or view fetch and render into the active file. An issue favorite renders that one issue in the buffer as its own source -- its full subtree (description, comments, drawer), the same as every other source. The remaining non-list favorites (document, dashboard, ...) open in the browser instead. Favorites are picker entries, never persisted -- a chosen favorite resolves to a concrete source before rendering, so refresh re-runs that resolved source and stays stable even if your favorites list later changes. Label and user favorites resolve by id, not by name or email, so renames in Linear don't break a saved fetch.
-To open a single issue you don't have favorited, use =pearl-open-issue-by-id= (=C-; L f i=, or =i= in the transient). Type an identifier like =ENG-123= (or a raw issue id) and Pearl fetches and renders that one issue. Handy when someone hands you an issue id and you'd rather have it in Pearl than a browser tab.
+To open a single issue you don't have favorited, use =pearl-open-issue-by-id= (=C-; L f i=, or =i= in the transient). Type an identifier like =ENG-123= (or a raw issue id) and Pearl fetches and renders that one issue. Handy when someone hands you an issue id and you'd rather have it in Pearl than a browser tab. The identifier is the command's only argument, so a script or an assistant can open an issue for you from outside Emacs. The call returns as soon as the fetch is queued, so its exit status says nothing about the result; the issue (or an error) shows up in Emacs:
+
+#+begin_src bash
+emacsclient -e '(pearl-open-issue-by-id "ENG-123")'
+#+end_src
A local view you've published to Linear (see [[*Publishing a local view as a Linear view]] below) renders as =[local → Linear:<Team or Personal>] Name= so you can see at a glance that it's published and to which scope. The arrow reads "this local view is mirrored there." The local view is the source of truth: picking it runs *your local filter*, not the Linear mirror, so editing the local view and running it shows your edits even before you publish them. To run the server-side Linear view instead, use =pearl-run-linear-view=. Plain =[local]= entries are local-only. =[local → Linear:?]= means the entry is published but Pearl couldn't resolve the team id (deleted or renamed on Linear) -- running still works, the label is just flagging stale scope metadata.