On 08/05/2016 07:48 μμ, alx wrote:
> Hi, I just tested it on FreeBSD (don't have a Linux VM), but that
> shouldn't make much difference in this case.
>
> Make sure you're getting the right client name with:
> $ xprop | grep WM_CLASS
>
> The output for the chosen window should be something like:
>
On 08/05/2016 07:48 μμ, alx wrote:
> Hi, I just tested it on FreeBSD (don't have a Linux VM), but that
> shouldn't make much difference in this case.
>
> Make sure you're getting the right client name with:
> $ xprop | grep WM_CLASS
>
> The output for the chosen window should be something like:
>
Hi, I just tested it on FreeBSD (don't have a Linux VM), but that
shouldn't make much difference in this case.
Make sure you're getting the right client name with:
$ xprop | grep WM_CLASS
The output for the chosen window should be something like:
WM_CLASS(STRING) = "xclock", "XClock"
The quoted
On 08/05/2016 04:19 μμ, Antonis Tsolomitis wrote:
> On 05/05/2016 04:53 μμ, alx wrote:
>> On 05/05/16 13:22, Antonis Tsolomitis wrote:
>>> Number 2 above
>>> can be partly bypassed if one manages to theme pavucontrol;
>>> but the
>>> docked volume control is needed.
>>
>> Perhaps the front p
On 05/05/2016 04:53 μμ, alx wrote:
On 05/05/16 13:22, Antonis Tsolomitis wrote:
Number 2 above
can be partly bypassed if one manages to theme pavucontrol; but
the
docked volume control is needed.
Perhaps the front panel's ability to capture X clients may be of help
here (provided ther
