Re: history and hotlist not saved; CSS site

2017-04-28 Thread Nick Roberts
In message <5ea82c6b-73ca-6728-a118-e7111d094...@codethink.co.uk> Michael Drake wrote: > > On 28/04/17 11:18, Michael Drake wrote: > > > > We could change it not to save the hotlist on exit when > > an external hotlist manager is used, since that would > >

Re: history and hotlist not saved; CSS site

2017-04-28 Thread Michael Drake
On 28/04/17 11:18, Michael Drake wrote: We could change it not to save the hotlist on exit when an external hotlist manager is used, since that would be a simple change. Done.

Re: history and hotlist not saved; CSS site

2017-04-28 Thread Michael Drake
On 28/04/17 10:51, Michael Drake wrote: In any case, I can make it more robust by consulting the external hotlist option before removing from the hotlist. Actually it already does that, so NetSurf shouldn't be saving the hotlist when the hotlist is edited, when configured to use an external

Re: history and hotlist not saved; CSS site

2017-04-28 Thread Michael Drake
On 27/04/17 18:03, Michael Drake wrote: On 26/04/17 18:30, Nick Roberts wrote: Can you just confirm that NetSurf doesn't save the file if there is an external hotlist manager? I don't know, off the top of my head. I'm unfamiliar with the external hotlist option. If I have time tomorrow I