sawfish-client errors end up in .xsession-errors
Bug #175084 reported by
era
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| sawfish (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
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.
| Changed in sawfish: | |
| status: | New → Confirmed |
Revision history for this message
| Christopher Bratusek (zanghar) wrote | #3 |
To post a comment you must log in.
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-
user> (get-window-
user> ^D
vnix$ tail -3 .xsession-errors
*** Unbound variable: nosvchcommand
*** Bad argument: #<subr string-match>, invalidparameter, 1
*** Required argument missing: #<closure get-window-