mirror of
https://github.com/org-roam/org-roam
synced 2025-08-29 14:33:29 -05:00
Deploying to gh-pages from @ feb9179c9f
🚀
This commit is contained in:
14
manual.html
14
manual.html
@@ -1573,7 +1573,19 @@ file:
|
|||||||
</pre></div>
|
</pre></div>
|
||||||
|
|
||||||
<p>We also need to set up <code>org-protocol</code>: the instructions for setting up
|
<p>We also need to set up <code>org-protocol</code>: the instructions for setting up
|
||||||
<code>org-protocol</code> are reproduced below.
|
<code>org-protocol</code> are reproduced here.
|
||||||
|
</p>
|
||||||
|
<p>On a high-level, external calls are passed to Emacs via <code>emacsclient</code>.
|
||||||
|
<code>org-protocol</code> intercepts these and runs custom actions based on the protocols
|
||||||
|
registered. Hence, to use <code>org-protocol</code>, once must:
|
||||||
|
</p>
|
||||||
|
<ul>
|
||||||
|
<li> launch the <code>emacsclient</code> process
|
||||||
|
|
||||||
|
</li><li> Register <code>org-protocol://</code> as a valid scheme-handler
|
||||||
|
</li></ul>
|
||||||
|
|
||||||
|
<p>The instructions for the latter for each operating system is detailed below.
|
||||||
</p>
|
</p>
|
||||||
<table class="menu" border="0" cellspacing="0">
|
<table class="menu" border="0" cellspacing="0">
|
||||||
<tr><td align="left" valign="top">• <a href="#Linux" accesskey="1">Linux</a></td><td> </td><td align="left" valign="top">
|
<tr><td align="left" valign="top">• <a href="#Linux" accesskey="1">Linux</a></td><td> </td><td align="left" valign="top">
|
||||||
|
11
org-roam.org
11
org-roam.org
@@ -902,7 +902,16 @@ file:
|
|||||||
#+END_SRC
|
#+END_SRC
|
||||||
|
|
||||||
We also need to set up ~org-protocol~: the instructions for setting up
|
We also need to set up ~org-protocol~: the instructions for setting up
|
||||||
~org-protocol~ are reproduced below.
|
~org-protocol~ are reproduced here.
|
||||||
|
|
||||||
|
On a high-level, external calls are passed to Emacs via ~emacsclient~.
|
||||||
|
~org-protocol~ intercepts these and runs custom actions based on the protocols
|
||||||
|
registered. Hence, to use ~org-protocol~, once must:
|
||||||
|
|
||||||
|
1. launch the ~emacsclient~ process
|
||||||
|
2. Register ~org-protocol://~ as a valid scheme-handler
|
||||||
|
|
||||||
|
The instructions for the latter for each operating system is detailed below.
|
||||||
|
|
||||||
*** Linux
|
*** Linux
|
||||||
For Linux users, create a desktop application in
|
For Linux users, create a desktop application in
|
||||||
|
@@ -1309,7 +1309,21 @@ file:
|
|||||||
@end lisp
|
@end lisp
|
||||||
|
|
||||||
We also need to set up @code{org-protocol}: the instructions for setting up
|
We also need to set up @code{org-protocol}: the instructions for setting up
|
||||||
@code{org-protocol} are reproduced below.
|
@code{org-protocol} are reproduced here.
|
||||||
|
|
||||||
|
On a high-level, external calls are passed to Emacs via @code{emacsclient}.
|
||||||
|
@code{org-protocol} intercepts these and runs custom actions based on the protocols
|
||||||
|
registered. Hence, to use @code{org-protocol}, once must:
|
||||||
|
|
||||||
|
@itemize
|
||||||
|
@item
|
||||||
|
launch the @code{emacsclient} process
|
||||||
|
|
||||||
|
@item
|
||||||
|
Register @code{org-protocol://} as a valid scheme-handler
|
||||||
|
@end itemize
|
||||||
|
|
||||||
|
The instructions for the latter for each operating system is detailed below.
|
||||||
|
|
||||||
@menu
|
@menu
|
||||||
* Linux::
|
* Linux::
|
||||||
|
Reference in New Issue
Block a user