Closed tyalie closed 2 years ago
This is the normal behavior. There's no "global clipboard" on Wayland or X11; applications provide clipboard contents on demand. This means that wl-copy must run in the background and serve the clipboard contents until something else replaces them.
ah oke that makes sense. so I might need to find another way to do this
Essentially the problem is:
wl-copy
doesn't close after finishing it's job. It took me a while to identify it as a problem, but independent on whether it is forked or run in foreground, the program will hang after copying the input. Interestingly enough it will close after a newwl-copy
instance was run (which in turn doesn't close until a replacement occurs, ...)It becomes annoying when the terminal emulator one uses waits for all forked processes to close after the shell has been stopped - which in turn doesn't happen here or after copying something in neovim (which uses wl-copy) the wl-copy command will still run in the background even though neovim has been terminated.
Another observation is, that
wl-copy
will respond to a normalSIGTERM
and terminate accordingly. So it isn't really frozen here.Examples
System config