[README] Still 6 patches to test + Open Goals

Re: [README] Still 6 patches to test + Open Goals

On Mon, Dec 15, 2008 at 10:06 AM, Christopher Bratusek
<nano-master <at> gmx.de> wrote:
> Hi all,
>
> Just 5 more days 'till sawfish 1.3.5. So I invite everyone to test the 6
> patches which are submitted.
>
> And there are also some open goals, assigned to andrea: Do you think you get
> them finished, or
> do you want to move them to goals for 1.3.6? see:
> http://sawfish.wikia.com/wiki/Proposed_Goals
> I'll now move any unassigned goal to 1.3.6.
>

For stagger placement I'll post a patch tomorrow (it's a one liner),
for sawfish-ui disconnected when restarting I have not yet found a
solution, I was looking on how to make the communication persistent.

> One more thing: any solution for this here?
> http://mail.gnome.org/archives/sawfish-list/2008-November/msg00064.html
>

I'm still using a Sawfish stable version and I can't replicate it here
(Debian Sid, Gnome 2.20/2.22), I probably need to test it with an
updated SVN version.

--

-- 
Andrea

Re: [README] Still 6 patches to test + Open Goals

On Mon, Dec 15, 2008 at 10:06:22AM +0100, Christopher Bratusek wrote:
> 
> One more thing: any solution for this here? http://mail.gnome.org/archives/sawfish-list/2008-November/msg00064.html

Did you try to check what xwininfo has to say about this particular
window?

    Michal

Re: [README] Still 6 patches to test + Open Goals

Re: [README] Still 6 patches to test + Open Goals

Re: [README] Still 6 patches to test + Open Goals

On Tue, Dec 16, 2008 at 10:31 AM, Christopher Bratusek
<nano-master <at> gmx.de> wrote:

> ( add-window-matcher 'WM_CLASS "^Mixer_applet2/mixer_applet2$" '( frame-type
> . none ))
>
> does also not solve the problem ... I'm using gnome 2.25x (selfcompiled from
> SVN) perhaps there has been some change in the mixer-applet's window-type?

Checked with a Sawfish SVN snapshot (revision 4311) and a clean
configuration, the mixer-applet is not decorated. To exclude a Sawfish
regression, I would try with a different WM, like FVWM for example.

--

-- 
Andrea

Re: patch testing howto

On Wed, Nov 26, 2008 at 12:46 PM, Teika Kazura <teika <at> lavabit.com> wrote:
> Hi, folks.
>
> As I wrote in another post, I ask you to share your knowledge on
> patch testing. I've made a wiki page:
> http://sawfish.wikia.com/wiki/Patch_testing_howto
> Please expand the list below, by answering in the email or
> by editing the wiki, whichever way you prefer.
>

I install an updated SVN version in a local dir on my home, and I
execute it in a Xephyr instance with a different user (the ~/.xsession
point the binary in my home).

If it's a C patch I reinstall it completely (make install), if it's a
Lisp patch, I simply modify the .jl files and restart Sawfish (if both
.jl and .jlc files are available, it will load the more recent of the
two).

--

-- 
Andrea

Re: [README] Still 6 patches to test + Open Goals

On Tue, Dec 16, 2008 at 10:20:49AM +0100, Christopher Bratusek wrote:
> Am Montag, den 15.12.2008, 19:01 -0700 schrieb Michal Jaegermann:
> 
>     On Mon, Dec 15, 2008 at 10:06:22AM +0100, Christopher Bratusek wrote:
>     >
>     > One more thing: any solution for this here? http://mail.gnome.org/archives/sawfish-list/2008-November/msg00064.html
> 
>     Did you try to check what xwininfo has to say about this particular
>     window?
> 
>         Michal
> 
> xwininfo: Window id: 0x4000032 "Lautstärkeregler"

Hm, I guess that 'xprop' may have something more interesting to say
about it.  WM_CLASS, WM_NAME and WM_STATE in particular.

There will be likely quite copious output.  I do not think that you
have to post it all. 

    Michal

Re: [README] Still 6 patches to test + Open Goals

Re: [README] Still 6 patches to test + Open Goals

On Tue, Dec 16, 2008 at 09:19:50PM +0100, Christopher Bratusek wrote:
> Am Dienstag, den 16.12.2008, 12:12 -0700 schrieb Michal Jaegermann:
> 
> 
>     Hm, I guess that 'xprop' may have something more interesting to say
>     about it.  WM_CLASS, WM_NAME and WM_STATE in particular.
....

> WM_HINTS(WM_HINTS):
> Client accepts input or input focus: True
> Initial state is Normal State.
> bitmap id # to use for icon: 0x3e00038
> bitmap id # of mask for icon: 0x3e0003a
> window id # of group leader: 0x3e00001
> _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0

I will not tell from the top of my head what all that means. But
checking headers and sources may show something interesting.

> WM_CLASS(STRING) = "mixer_applet2", "Mixer_applet2"

And you do: 

( add-window-matcher 'WM_CLASS "^Mixer_applet2/mixer_applet2$"
   '( frame-type .  none ))

It looks to me that this regexp should be "^[Mm]ixer_applet2$"
although ".ixer_applet2$" is likely good enough (or you may add
an ^ anchor too).   Just guessing...

    Michal