omgold

I did take a look. The origin of the issue is this ``` content = window.as_text(as_ansi=True, add_history=True, add_wrap_markers=True) ``` Using `add_wrap_markers` is what gives you the undesired line breaks. Unfortunately...

An (imperfect) workaround would be to assume there should be no line break when the line has as many characters as the window width: ``` diff --git a/_grab_ui.py b/_grab_ui.py index...

I'm aware. The issue of unicode combiners and wide characters can't be fixed so easily, I guess. About curses windowed interfaces like mc, I wouldn't particularly mind. Don't know why...

Another (rather insane) method would be to fetch 2 copies of the contents from kitty, one with extra line breaks, one without, and then reconstruct from that which line breaks...

In emacs I'm used to use the 'move to prev/next empty line' feature (ctrl+arrows). WIth text files this usually works well enough, but as on the shell there are rarely...

> This sounds like a duplicate of #8243 @bt90 Can you explain? That ticket seems to be about a memory leak and hanging udp sockets, no? My issue is presumedly...

Doesn't look like. What exactly is supposed to be restarted automatically? The whole process?

Okay, seems I found the issue, then: The code to detect the restart is this ``` if time.Since(now) > 2*time.Minute && cfg.Options().RestartOnWakeup { l.Infof("Paused state detected, possibly woke up from...

@AudriusButkevicius The quote from the manual explains it. `time.Since()` does not calculate the difference in wallclock time, but monotonic time. And monotonic time is apparently halted during system suspend.

Yeah, quite a bit counterintuitive. The fix is simple, though: ``` --- src/github.com/syncthing/syncthing/cmd/syncthing/main.go.orig 2022-05-14 15:13:31.192225539 +0200 +++ src/github.com/syncthing/syncthing/cmd/syncthing/main.go 2022-05-14 15:13:52.694070436 +0200 @@ -763,7 +763,7 @@ func standbyMonitor(app *syncthing.App, cfg config.Wrapper)...