Table of Contents
This is an attempt to capture some of the questions that appear once in a while on the mailing list.
ELinks instances connect together so that they share the cache, bookmarks, cookies, configuration, etc. Only the "master" ELinks instance does any real work and any other ELinkses you run will only connect to this instance. So when you want to restart ELinks, make sure you have no other ELinks instances running at the time.
Alternatively, you can use the -no-connect
parameter to make the ELinks
always run standalone, or create a parallel group of ELinks instances by the
-session-ring N
parameter (where N
is a number larger than zero); however,
be aware of the fact that in those cases ELinks won't touch any configuration,
bookmark, cookies, etc files - you can force that by the -touch-files
parameter, however beware - this can result in a data loss! (E.g., when two
master ELinks instances will try to save their bookmarks and you add a
bookmark to each of those, only one of the bookmarks survives.)