Sawfish documentation states (in several places) things like that: 4. How do I add customizations? There are several files controlling this: `~/.sawfishrc' Hand written lisp code, loaded at startup. This is where almost all explicit customization should be done. This does not correspond to reality. Actually checking files in /usr/share/sawfish/0.34/lisp/ one can see that only ~/.sawmillrc is referenced in grow-pack.jl and ~/.sawmillrc actually gets loaded. OTOH sawfish package includes a script like /usr/bin/sawmill-replace.sh Michal michal
I use ~/.sawfishrc with the current build (although I think it still will support a ~/.sawmillrc). We do ship with some default settings but all can be nulled with information in ~/.sawfishrc Have you tried creating one to no success? What is the problem specifically?
> Have you tried creating one to no success? Well, yes, hence the bug report. With the following line in ~/.sawfishrc (system "xclock -padding 2 -title '' -bg lightgray -geometry 74x74+100+11 &") nothing happens. After linking ~/.sawfishrc to ~/.sawmillrc an expected clock face shows up. Yes, I know that I can do that in another way on a Gnome desktop, although not when I am running "pure sawfish"; this is just a test example.
Thats a fine test, thanks :) Assigning.
The file lisp/sawfish/wm/user.jl loads .sawfishrc as long as no .sawmillrc exists. Putting the xclock line in my .sawfishrc works fine for me (as long as I have no .sawmillrc).
Hm, interesting. If I would have both ~/.sawmillrc and ~/.sawfishrc then I would not notice that something does not work. OTOH once ~/.sawmillrc was in place then now ~/.sawfishrc gets loaded as well even if it is there only by itself. In any case grow-pack.jl seems to reference only ~/.sawmillrc.