aboutsummaryrefslogtreecommitdiff
path: root/README.org
diff options
context:
space:
mode:
Diffstat (limited to 'README.org')
-rw-r--r--README.org15
1 files changed, 15 insertions, 0 deletions
diff --git a/README.org b/README.org
index 0c78722..f6323f5 100644
--- a/README.org
+++ b/README.org
@@ -337,6 +337,21 @@ Most users only need an API key and an output path. The rest are knobs for teams
If a fetch stops at the pagination cap, Pearl writes =#+LINEAR-TRUNCATED: yes= in the file header. Raise =pearl-max-issue-pages= if your result set is larger than the default 1000 issues.
+*** Which browser opens for Linear URLs
+
+Pearl hands every URL it opens (issue links, view links, browser-only favorites) to Emacs's =browse-url=, which dispatches to whatever =browse-url-browser-function= names. Pearl never picks a browser of its own, so the answer to "why this browser?" is always your Emacs setting, not pearl. Your system default ($BROWSER, xdg-mime) only matters when =browse-url-browser-function= delegates to it.
+
+Common shapes:
+
+| Value | Behavior |
+|---------------------------------------------+----------------------------------------------------------------|
+| ='browse-url-default-browser= | Emacs autodetects (usually correct) |
+| ='browse-url-xdg-open= | Honor the desktop default (=xdg-mime= for http/https) |
+| ='browse-url-firefox= / =-chrome= / =-chromium= | Always that browser |
+| ='browse-url-generic= + =browse-url-generic-program= | Any command you name |
+
+For per-URL routing (e.g. "Linear goes to the work-account browser, everything else to my personal one"), set =browse-url-handlers= with a list of =(REGEXP . FUNCTION)= pairs.
+
** Development & Testing
:PROPERTIES:
:CUSTOM_ID: development--testing