On Mon, Apr 04, 2016 at 07:24:46PM +0100, Jose M Calhariz wrote: > It is possible to run the sawfish standalone in a terminal window for > collecting the error messages?
It didn't let me do that, but I was able to redirect the output to a file: Lisp backtrace: #6 open-structures ((rep rep.regexp rep.system rep.io.files rep.io.processes sawfish.wm sawfish.wm.util.groups sawfish.wm.util.display-window sawfish.wm.util.compat sawfish.wm.ext.error-handler sawfish.wm.ext.apps-menu sawfish.wm.edge.conf sawfish.wm.edge.actions sawfish.wm.frames sawfish.wm.menus sawfish.wm.commands.launcher sawfish.wm.ext.wallpaper sawfish.wm.prg.compton sawfish.wm.prg.conky sawfish.wm.prg.diodon sawfish.wm.prg.fehlstart sawfish.wm.prg.idesk sawfish.wm.prg.nm-applet sawfish.wm.prg.pancake sawfish.wm.prg.trayer sawfish.wm.prg.xgamma sawfish.wm.prg.xmobar sawfish.wm.prg.xmodmap sawfish.wm.prg.xsettingsd)) #4 make-structure (() #<closure 26af328 @ user> #<closure 26af300 @ sawfish.wm> user) #2 load ... #1 run-byte-code ... error--> (file-error "No such file or directory" "sawfish/wm/ext/wallpaper")
signature.asc
Description: PGP signature
