| Re: [Sawfish] Remove border for xterm |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/sawfish Archives
]
- To: sawfish@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [Sawfish] Remove border for xterm
- From: Teika Kazura <teika@xxxxxxxxxxx>
- Date: Thu, 08 Dec 2011 21:25:32 +0900 (JST)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=lavabit; d=lavabit.com; b=AsGvjSzvmIaIJLcRdg8YcsYEWzCP1smo99fWvdAsUGRSO66WlzbIJAAvu+4IMHuD9+3Dxm5CughWNHxrka6PGA2DZApwQ/wuUfxaKb/J40WTC/b8bT/Brwnp7wZzkZfMRA53Mmuv2/USKlOf7rAvGuHDiaviPJHvDSLcINzwCy8=; h=Date:Message-Id:To:Subject:From:In-Reply-To:References:Mime-Version:Content-Type:Content-Transfer-Encoding;
Hi, janemba.
First, I mistook one thing: starting order does *not* matter. Sorry.
One thing I forgot was ~/.sawfish/window-history. Renaming it (or
deleting if you don't need it.) may fix. (I don't understand what this file
is, so it may be irrelevant.) I never use it, but sometimes it's
generated automatically. So the script I use to start Sawfish checks
the existence of that file, and warns.
Hand-editing of ~/.sawfish/custom can be the last resort. Delete
*all* lines which contain match-window-profile (since you're grep
lover, I don't think you missed other lines, though.) and re-add
rules. Some rules which contain "frame-type normal" smell fishy. One
of them may be matching too to xterm for some reason. (Kill
configurators, restart Sawfish, edit and save, and restart Sawfish.)
Regards,
Teika (Teika kazura)
---
--
Sawfish ML