Re: Does adding bookmarks update the configuration ?
- From: <tpgww@xxxxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Thu, 4 Sep 2008 11:52:03 +1000
On Wed, 3 Sep 2008 21:39:07 -0400
Grégory SCHMITT <gy.schmitt@xxxxxxxxx> wrote:
> ----- Original Message -----
> > Date: Thu, 4 Sep 2008 11:29:34 +1000
> > De: <tpgww@xxxxxxxxxxx>
> > À: emelfm2@xxxxxxxxxxxxx
> > Sujet: Re: Does adding bookmarks update the configuration ?
>
> > 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 ?
>
> Is the default behaviour to have two different sessions of emelfm2 ? I
> honestly do not believe that, so my suggestion is to leave it as it is.
Who knows ?
> Furthermore, many users will change the configuration file by calling
> the config panel, not by editing the contents of the file directly.
I meant to change the _coded_ default setting, so that when a user has no
config file, or does a config dialog "Default" process, then replication will
be turned off.
I recall that one distro patched e2 like that. Arguably it's the failsafe way.
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.
Other related posts:
