Re: The mysterious disappearing match rules

Quoting Robert 'Bobby' Zenz <[email protected]> on Wed, Aug 31 20:08:
>
> In case you do not know how, here is a simple guide:
> 
>  1. Install Git.
>  2. Go to `~/.sawfish/`.
>  3. Run `git init`. It might complain about missing configuration, so
>  please to as it says.
>  4. Run `git add custom window-history`. This will mark the files for
>  the next commit.
>  5. Run `git commit -m "Added files."`.

One thing that could make this work significantly better is if Sawfish
formatted the config file in more of a line orientated manner. More
like this for the really long variables;

(custom-set-keymap 
 (quote window-keymap) 
 (quote (keymap 
         ((send-to-workspace 1) . "H-KP_Home") 
         (send-to-next-head     . "H-KP_Insert") 
         ((send-to-workspace 2) . "H-KP_Up") 
         (popup-window-menu     . "H-Button1-Off")
...etc

Even more awesome would be for Sawfish to sort by variable name before
writing the file. This would make `git diff' really able to show what had
changed in a way that would be easy to read.

I'm on version 3:1.11-1nano on Debian if it makes a difference.

-- 
Let's not cloud the issue with facts.

-- 
Sawfish ML