zim-wiki team mailing list archive

[Jaap Karssenberg <jaap.karssenberg@xxxxxxxxx>]

I think it makes sens to open a ticket. Also for other use cases if a user
is switching often between screens this can result in a lot of saves, so
sounds like a good fix to make.

Yes, there is a ton of other work in the tracker that I didn't even look at
- but opening a ticket for this kind of thing at least means it gets ranked
against all those items at some point :)

Regards,

Jaap



On Wed, Jan 31, 2018 at 5:30 PM Charles Nepote <charles@xxxxxxxxxx> wrote:

> Le 31/01/2018 à 12:55, Jaap Karssenberg a écrit :
>
> Current version it is hardcoded, so requires patch to disable.
>
> Maybe instead of just disabling, the logic should be refined to check the
> timer and only do the save if e.g. within 80% of the time to next save.
> Result would be that 10 minutes becomes somewhere between 8 and 10 minutes.
>
> Why not? But maybe just keep it simple ;-)
> Whatever, do you think I should open a ticket or there are really more
> important things?
> Regards,
> Charles.
>
>
>
> Regards,
>
> Jaap
>
>
> On Wed, Jan 31, 2018 at 12:33 PM Charles Nepote <charles@xxxxxxxxxx>
> wrote:
>
>> Got it. What is annoying for me is that Zim is synchronized and
>> versionned with Seafile: each saving also does a sync, which is not useful
>> and creates tons of versions.
>> Could it be disabled?
>>
>> Charles.
>>
>>
>>
>> Le 31/01/2018 à 11:15, Jaap Karssenberg a écrit :
>>
>> Yes it is a feature. Saving can cause hiccups in the application when
>> typing. So we try to schedule it when focus leaves the window.
>>
>> Jaap
>>
>> On Wed, Jan 31, 2018, 11:13 Charles Nepote <charles@xxxxxxxxxx> wrote:
>>
>>> Hi all!
>>>
>>> I'm facing an annoying behaviour (while not so important): when I write
>>> in Zim window and leave it for another window, Zim auto-save the current
>>> content, even if I told him to save every 10 minutes in the config file.
>>> Any idea?
>>>
>>> Charles.
>>>
>>
>