Admittedly yes I would've definitely expected that behavior.  Particularly
from the has-session command, since its entire method of operation is to
return an exit status; it could be argued with that behavior its purpose
is specifically to be used quietly in scripts.  I would expect -q to make
it silent when considering that.

However I understand if this behavior is not a bug and just my expectations
are simply different from the author's.  If this ticket is to be marked wont-fix
then I have no problem with that.  It's really just an annoyance anyway, not
a functional problem.


Romain Francoise <rfranco...@debian.org> writes:

>> The -q option intended for quiet operation does not appear
>> to be working in the version of tmux currently in sid (what
>> I am using).  For example, the has-session argument for tmux
>> is commonly used in scripts with -q as such:
>>
>> $ tmux -q has-session -t existingsession
>> $
>>
>> This would be the expected behavior, with an exit 0 status,
>> and this does work.  However, if I perform the command on a
>> session target that doesn't exist, I get:
>>
>> $ tmux -q has-session -t nonexistant
>> session not found: nonexistant
>> $
>>
>> The exit status is 1 as would be expected, so the has-session
>> function itself works.  It is just the -q that seems to be
>> ignored, since that should've been a silent operation.
>
> The -q flag doesn't suppress *all* messages as you seem to expect.
> It just disables some informational messages that would otherwise be
> annoying (e.g. when you toggle an option).
>
> It should be easy enough to just redirect the client's output to /dev/null
> as necessary.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to