Re: Does adding bookmarks update the configuration ?

  • From: "Adam Krolnik" <akrolnik@xxxxxxxxx>
  • To: emelfm2@xxxxxxxxxxxxx
  • Date: Wed, 3 Sep 2008 22:04:42 -0500

I'd definitely prefer to have bookmark updates be persistent. I expect to
use more than
one window for the time being.

I'd use the multiple output panes instead, but then I have to navigate back
to the directories that
I had setup on the panes for the other output tabs. Maybe if the directories
the panes contain were saved to the tab and switching output tabs meant
switching directories then it would be easier to
have one window...



On Wed, Sep 3, 2008 at 8:29 PM, <tpgww@xxxxxxxxxxx> wrote:

> On Wed, 3 Sep 2008 17:14:57 -0400
> Grégory SCHMITT <gy.schmitt@xxxxxxxxx> wrote:
>
> > ----- Original Message -----
> > > Date: Wed, 03 Sep 2008 15:56:12 -0500
> > > De: Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx>
> > > À: emelfm2@xxxxxxxxxxxxx
> > > Sujet: Does adding bookmarks update the configuration ?
>
> > > It appears that bookmarks are getting lost when I have two emelfm2
> > > windows open.
> > >
> > > If I add a bookmark in one then attend to another emelfm2 (newly
> > > opened I believe)
> > > and then close it, I lose the bookmark I just added.
> >
> > As you've probably noted, bookmarks are not updated in real-time, but
> > after emelfm2 is restarted.
> >
> > In other words, if you start two sessions of emelfm2 (1 and 2), edit
> > your bookmarks in 1, close 1 first and then 2, it makes sense to me
> > that bookmarks from 2 will overwrite 1 when 2 is closed.
>
> I'd put it like this: in-session bookmark changes are not saved to disk
> (config file) until the next "OK/Commit" in a config dialog, or session-end.
> If you are configured to refresh current configuration upon detecting change
> of config file (and the default is to do this), then a saved 2nd session
> will in effect overwrite a 1st session.
>
> Maybe we should change that default ?
>
> Regards
> Tom
>
>
> --
> Users can unsubscribe from the list by sending email to
> emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or
> by logging into the web interface.
>



-- 
Adam Krolnik

Other related posts: