Long breaks are not triggered

[buscon]

hi,

long breaks are not triggered, even though I set them in the settings. how can I debug the situation?

[slgobinath]

Hi, Please run Safe Eyes from the terminal using the following command and share the log. You will get the log file in the home directory.

safeeyes --debug

[leedoyle]

Confirming the issue, it is yet unclear to me when it sometimes happens (and then disappears).

[slgobinath]

it sometimes happens (and then disappears).

You mean you get the break sometimes but sometimes not?

Safe Eyes skips the next long break if you were idle for a period equal to a break duration. It was added to avoid getting a long break immediately when you start using your computer after a long idle period (say you went for lunch). You can test this behavior by running safe eyes in debug mode(safeeyes --debug) and checking for the information log: Skip next long break due to the pause longer than break duration.

[kael-shipman]

Ok I've just confirmed that at least in my case, I'm getting the Skip next long break due to pause... message. I'm content with that, although I think I would like an option to disable it or adjust it. I see the "Smart Pause" plugin, but that character of that plugin is a little different, as I see that as describing when to stop the clock, not whether or not to consider idle time as a break.

As for my use-case, it's important to me that the short breaks remain short so that I don't mind doing them, but I want to use the long breaks for periodic exercise, and that's why it's important that they continue as planned. I often get up and go to the bathroom or grab a snack or something, and the system apparently counts that as my long break, but getting a snack is NOT doing push-ups ;). And since those interruptions are unplanned, all that ends up happening is that I never do my push-ups.

I think my problem would be solved if there were an additional option in the "Long Breaks" config section that just said, "Skip next long break if idle for an equivalent duration." If that's on, then we do current functionality. If it's off, then long breaks are always taken as planned.