Hello,
While using xfontsel 1.06, I noticed that the 'select' button writes to
the PRIMARY buffer in an unconventional way.
Some programs can't read the PRIMARY after this is done.
Steps to reproduce:
1) run `autocutsel -s PRIMARY -verbose -debug` (to track PRIMARY)
1) run `xfontsel` from t
Hi,
While using xfontsel 1.06, I noticed that it copies to the PRIMARY
buffer in a non-standard way
where certain applications aren't able to read the contents of PRIMARY
after the 'select' button is pressed.
For example, `xautosel -s PRIMARY -verbose -debug` does not print
anything after the sele
