Rafa? Krzewski wrote:
Maybe not ... :) After a while of stracing I discovered that sawfish was notreading the same file that it was writing the settings to.Configuration is being written to ~/.sawfish/custom, but the files loaded atstartup are ~/.sawfishrc ~/.sawfishrc.jl ~/.sawfishrc.jlc ~/.sawfish/lisp/site-init ~/.sawfish/lisp/site-init.jl ~/.sawfish/lisp/site-init.jlc ~/.sawmillrc etc.
... and after reading sawfish/wm/user.jl I discovered that the issue is more complicated than that. I'm none of a scheme hacker, but as far as I can tell custom-load-user-file function is failing to load the file that is successfuly loaded by safe-load function few lines further down. I'm not seeing any relevant error messages in any of the ~/*-errors files though (BTW. where is sawfish's stderr going?).
Creating a symbolic link from ~/.sawfish/custom to ~/.sawfishrc fixes the problem.
Which is a working stop-gap solution until the problem is fixed upstream.... Rafal
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature