Hi Florian,
thanks for the heads up. So far I think the current features work for my use
case. Nonetheless, Ram-> is putting together very interesting ideas.
Cheers,
Pablo.
On jueves, 23 de julio de 2020 13:57:03 (CEST) Florian Bruhin wrote:
> Hey,
>
> On Thu, Jul 23, 2020 at 11:58:29AM
Hey,
On Thu, Jul 23, 2020 at 11:58:29AM +0200, J Pablo Navarro wrote:
> I'm successfully using the setup Simon described in a previous email. The
> thing is I cannot manage to use different session and keep them separated.
>
> In order to open a previously saved session, I need a qutebrowser
Hello again,
I'm successfully using the setup Simon described in a previous email. The
thing is I cannot manage to use different session and keep them separated.
In order to open a previously saved session, I need a qutebrowser window.
Usually that window is the default session for my machine.
Hi Florian,
> FWIW I don't think anything changed about that - the session files were always
> read at the point you run the :session-load completion/command.
I'm sorry, I didn't express myself correctly. I said "load" while this means to
"load the session in Qutebrowser", but what I really
Hey,
On Sun, Jul 05, 2020 at 04:44:58PM -0400, Simon Désaulniers wrote:
> I have noticed recently (after some upgrade) that Qutebrowser even now
> reloads session files when they change on disk (it wasn't the case a few
> months ago I think).
FWIW I don't think anything changed about that - the
Hi J Pablo,
I recommend that you look into Syncthing [1]. This is a cross platform syncing
software which operates in a decentralized and end-to-end (E2E) encrypted manner
for syncing files. On the surface, it works pretty much like any directory
syncing solution such as the well-known website
Hi,
There's a sessions directory in your data directory
(~/.local/share/qutebrowser by default, check :version if it's not). I'm
not sure all sessions there could be shared, though. AFAIK there's no
machine-specific information (in my current sessions) but there might
be.
Sincerely,
Felix