sawfish-client errors end up in .xsession-errors

[era]

Binary package hint: sawfish

When communicating with a running sawfish process from sawfish-client, any error messages end up on the parent sawfish's standard error, which in practice in most cases is redirected to .xsession-errors (or, worse yet, simply discarded). I can see how it might be architecturally a challenge to fix this, but it would be very useful indeed if responses to sawfish-client requests could be passed back and displayed by sawfish-client.

[era (era)]

Here's an example transcript, from a Gutsy installation.

vnix$ sawfish-client
sawfish 1.3, Copyright (C) 1999-2000 John Harper
sawfish comes with ABSOLUTELY NO WARRANTY; for details see the file COPYING

Enter `,help' to list commands.
user> (nosvchcommand)
(You're accessing an undefined variable or function `nosvchcommand')
user> (get-window-by-name-re 'invalidparameter)
user> (get-window-by-name-re) ; too few parameters
user> ^D

vnix$ tail -3 .xsession-errors
*** Unbound variable: nosvchcommand
*** Bad argument: #<subr string-match>, invalidparameter, 1
*** Required argument missing: #<closure get-window-by-name-re>, 1

[era (era)]

> Here's an example transcript, from a Gutsy installation.

Sorry, my bad, that was meant to say Feisty. I'll see if it's any different under Gutsy, but I would suspect not.

[Christopher Bratusek (zanghar)]

Indeed. Putting this on the TODO-List.