1
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 11. Managing remote ELinks instances</title><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"><link rel="start" href="index.html" title="The ELinks Manual"><link rel="up" href="index.html" title="The ELinks Manual"><link rel="prev" href="ch10s06.html" title="Some Sample Mailcap Entries"><link rel="next" href="ch11s02.html" title="Remote Actions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 11. Managing remote ELinks instances</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch10s06.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch11s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2520609"></a>Chapter 11. Managing remote ELinks instances</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch11.html#id2520673">Limitations and outstanding issues</a></span></dt><dt><span class="section"><a href="ch11s02.html">Remote Actions</a></span></dt></dl></div><p>Some programs provide the ability to pass URIs to external programs. When
1
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 11. Managing remote ELinks instances</title><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"><link rel="start" href="index.html" title="The ELinks Manual"><link rel="up" href="index.html" title="The ELinks Manual"><link rel="prev" href="ch10s06.html" title="Some Sample Mailcap Entries"><link rel="next" href="ch11s02.html" title="Remote Actions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 11. Managing remote ELinks instances</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch10s06.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch11s02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2521181"></a>Chapter 11. Managing remote ELinks instances</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch11.html#id2521245">Limitations and outstanding issues</a></span></dt><dt><span class="section"><a href="ch11s02.html">Remote Actions</a></span></dt></dl></div><p>Some programs provide the ability to pass URIs to external programs. When
2
2
stumbling upon a reference to a page you want to see, it is sometimes a kludge
3
3
to copy and paste it into ELinks. This is where -remote can be a nifty
4
4
solution.</p><p>When invoking ELinks with the -remote argument, it does not start a new
5
5
instance, but instead connects to an already running ELinks, making it
6
6
possible to control that ELinks instance. The -remote command line switch
7
7
takes a command consisting of the action to invoke and any parameters to the
8
action. Here is an example for opening freshmeat.net in a new tab:</p><pre class="literallayout">$ elinks -remote "openURL(http://freshmeat.net/, new-tab)"</pre><p>When running this command in a terminal, you will see a small delay before
8
action. Commands must begin with a nonempty sequence of ASCII alphabetic
9
characters followed by optional whitespace and an opening parenthesis. They
10
must end with a closing parenthesis optionally followed by whitespace. Here is
11
an example for opening freshmeat.net in a new tab:</p><pre class="literallayout">$ elinks -remote "openURL(http://freshmeat.net/, new-tab)"</pre><p>When running this command in a terminal, you will see a small delay before
9
12
ELinks returns. If no running instance was found, it will return with the
10
13
error message:</p><pre class="literallayout">ELinks: No remote session to connect to.</pre><p>All URLs passed to the openURL() commands can be URL prefixes, so the command
11
above could have simply used “openURL(fm, new-tab)”.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2520673"></a>Limitations and outstanding issues</h2></div></div></div><p>Remote control is implemented using the intercommunication socket created in
14
above could have simply used “openURL(fm, new-tab)”.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2521245"></a>Limitations and outstanding issues</h2></div></div></div><p>Remote control is implemented using the intercommunication socket created in
12
15
~/.elinks/, so the command has to be run on the same machine as the instance
13
16
you want to control; or put differently: the two ELinkses need to share a file
14
17
system that supports socket files, which rules out usage of -remote over NFS.
added
removed
doc/html/manual.html-chunked/ch11.html
