Re: Sawfish problems

[Mark Gordon <mtgordon helixcode com>]

Kevin D. Knerr, Sr. wrote:

> On 12 Oct, Telsa Gwynne wrote:
(snip) 
> > I think (b) sucks :)
> 
> Which is why I'm so surprised that the suggestion comes up so frequently
> on both the GNOME and sawfish lists . . .
> 
> Ripping it out is the MS-way of fixing a config problem.
> 
> Renaming the config file, say ~/.sawfishrc.ori is the *nix way . . .
(snip)
> In short, standard practice when a new release breaks config files
> should be to backup your originals (say, by renaming them), then add
> back each item, either via the user interface or by editing the config
> files. In sawfish's case, these are ~/.sawfishrc & ~/.sawfish/custom.

I reproduced the recent Helix Code sawfish problems with a user that had
no ~/.sawfish/custom, so I'm not convinced the most recent problems had
anything to do with breaking backward compatibility in ~/.sawfish/custom
(at least, not this time).

I think at least part of the problem is that we're typically trying to
upgrade a running sawfish.  In the course of uninstalling the old
sawfish, we pull the run-time dependency tablecloth out from under the
running sawfish.  I wonder whether the nuke-.sawfish-and-kill-X solution
is an overly brutal method of killing the old sawfish and starting the
new one (like Telsa, I've also heard reports changing the theme works
just as well, though I haven't confirmed this).  We need to find an
effective technique that's minimally violent.  Of course, the MS-way of
fixing this problem is to require a reboot. ;-)

-- 
-Mark Gordon