Re: Two instances of galeon sharing $HOME/.galeon

On Mon, Jul 11, 2005 at 03:16:00PM +0100, Crispin Flowerday did utter:
> 
> As long as you don't run galeon at the same time on both machines,
> things will be fine. 

That's not really possible with my current usage... I tend to run galeon
for weeks on end (and accumulate tabs like I used to accumulate
bookmarks) on my main machine... the secondary machine is more likely
to be rebooted, or at the least, logged off for the sake of someone
else, as it's more likely to be truly multiuser

> The alternative is to symlink ~/.galeon to a different the directory on
> the local machines (e.g. I have ~/.galeon symlinked
> to /space/crispin/home/dot_galeon). The only problem with the symlink
> method is that bookmarks aren't shared, but that has never really
> bothered me.

Hmm... point. Doable... and I'm sure even the bookmarking could be
solved with a bit of scripting to generate a clickable .html (or maybe
galeon should just be able to open up .xbel files in the myportal:
rendering? ;)

The only other solution which struck me (though it's not possible now,
may not even be possible at all, and probably not worth implementing
even if it is) would be to allow one galeon process to open each new
window to a different $DISPLAY if specified... I already have
transparent X11 forwarding between all the boxes in the house... ;)

.../Nemo
-- 
  ------------------------------------------ --------------------------
                                                    earth native


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar