You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of xclip 0.13, using xclip in a pipeline requires the user to explicitly add the -filter argument. Changing the default value from -silent to isatty(stdout) ? -silent : -filter would remove this need. The user could then write
foo | xclip | bar
# instead of
foo | xclip -filter | bar
The text was updated successfully, but these errors were encountered:
Janfel
changed the title
Decide input/output mode based on whether stdin is interactive.
Default to -filter instead of -silent in a pipeline.
Feb 3, 2021
I agree with this suggestion. Making the most common case the easiest makes sense to me. If a script wants to ensure a specific mode instead of relying on autodetection, it could always specify -in/-out/-filter.
However, the maintainer of xclip is not yet convinced that using isatty() a good idea. Feel free to weigh in on #88 if you have any helpful thoughts.
As of
xclip 0.13
, usingxclip
in a pipeline requires the user to explicitly add the-filter
argument. Changing the default value from-silent
toisatty(stdout) ? -silent : -filter
would remove this need. The user could then writeThe text was updated successfully, but these errors were encountered: