Icelk

I agree, it would make sense if `wait` passed the exit code, but without `wait`, the task ignores the exit code(s).

That seems like a good default.

Can confirm. But that's weird. When i `grep` on my system (with all deps of clipcat in the cargo repo), I get no results. It's nowhere in the clipcat codebase....

It seems to recover when I stop spamming it. Perhaps something with clipcat's gRPC implementation, which defaults to say 32 max concurrent clients?

Why would clipcatd initiate multiple connections to X? Form my experience (not much) clipcatd creates a connection at start, and keeps it.

I believe the date is already saved. https://github.com/xrelkd/clipcat/blob/21b1192213741a42f5a79d00eeb382c323f54ee7/src/lib.rs#L79 The only thing is accessing it through clipcat-menu.

I presume the code in `bin/clipcat-menu/` needs to output the date to the finder (how do we do this?). It should have access to the object, `ClipboardData`, which contains the...

Hi @jonaz ! I suspect this has to do with #19 Have you restarted xorg or your window manager while clipcatd was running. If so, just restart the daemon. Hope...

Weird, it works for me, using `i3-msg restart` which should do the exact same thing. Try clearing your clipboard cache and see if the issue persists.

Could you include your config? Are all the socket ports the same in all the configs? Did you try clearing the cache? `clipcatctl clear` IIRC