Re: [ANNOUNCE] Sawfish 1.6.1 "Astral". : sawfish restart bugs, short report.



Am Wed, 20 Jan 2010 21:41:27 +0100
schrieb Janek Kozicki <janek_listy wp pl>:

> Christopher Roy Bratusek said:     (by the date of Wed, 20 Jan 2010
> 21:26:29 +0100)
> 
> > > (1600*2+1920)*7 = 35840
> 
> I verified it even more precisely. This breaks exactly after 32768th
> pixel is exceeded. Therefore: after 'sawfish restart' all windows
> (except the maximized ones) are in their correct position. But if I
> try to move windows that are far-right (after 2^15 pixels) they behave
> wrongly. Which can be quickly fixed with grow-pack.
> 
> > > 
> > > 
> > > - and merlin ugliness, once again stopped being present. What is
> > > the current method to enable it. Is it now moved inside 1.6.1 ?
> > > 
> > > I am talking about that Alt-Tab feature for switching windows,
> > > remember? With merlin it displays all windows altogether.
> > 
> > do you mean the sawfish-merlin package comming from Debian? I don't
> > know if it's in standard load-path (or in debians extended
> > load-path). But a normal require merlin.blah should do the trick.
> 
> Yes, the debian native one.
> 
> Unfortunately I am getting some 'beep' and no error message.
> 
> When I copied all those *.jl to ~/.sawfish/ I got an error message
> "trying to use expert which does not exist". So I removed all
> references to "expert" from uglicon.jl file, and then again I am
> getting just a beep. But no message. And merlin still doesn't load.

I guess `expert' should be `export'

What does happen when using the original one from merlin.org?

> > 
> > > - and my sawfish-pager stopped working too. Did you put
> > > sawfish-pager into your debian deb-src repository too? I could
> > > try recompiling this one.
> > 
> > It always had been in my repo. And for this release it's somewhat
> > common to reinstall it.
> > 
> > >   OK, I downloaded 7.2 and another thing - it seems that in order
> > > to have the working option "Use X to mark current viewport" I
> > > need to comment out line #ifdef FRAMEOVER in the pager.c source
> > > at line 390. Why?
> > 
> > make -DFRAMEOVER

It's not me who added it. It's invalid in GIT

> ok, why do we need this flag? (it works nevertheless).
>  
> > > - clicking on sawfish's error message sends something to focused
> > >   window. An xterm with vim inside is scrolled up. Weird. 
> > 
> > Strange, I never had such issues.
> 
> 
> I tried to identify the event in xev, but that's hard. xev produces
> too much noise:
> 
> 
> 
> 
> VisibilityNotify event, serial 30, synthetic NO, window 0xa000001,
>     state VisibilityUnobscured
> 
> Expose event, serial 30, synthetic NO, window 0xa000001,
>     (0,332), width 641, height 40, count 0
> 
> EnterNotify event, serial 30, synthetic NO, window 0xa000001,
>     root 0x2a0, subw 0x0, time 1480040757, (81,352), root:(2346,601),
>     mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
>     focus NO, state 272
> 
> KeymapNotify event, serial 30, synthetic NO, window 0x0,
>     keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0
> 0   0 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 
> FocusIn event, serial 30, synthetic NO, window 0xa000001,
>     mode NotifyNormal, detail NotifyNonlinear
> 
> KeymapNotify event, serial 30, synthetic NO, window 0x0,
>     keys:  4294967200 0   0   0   0   0   0   0   0   0   0   0   0
> 0   0   0 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
> 0   
> 
> ButtonRelease event, serial 30, synthetic NO, window 0xa000001,
>     root 0x2a0, subw 0x0, time 1480040819, (81,352), root:(2346,601),
>     state 0x110, button 1, same_screen YES
> 
> 
> 
> The last ButtonRelease is when I release the mouse button, after the
> sawfish's error message window disappears.
> 
> Heh, tried to reproduce it again with vim ran inside xterm - succeeded
> after third try. So maybe this xev log isn't containing the offensive
> event....
> 
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]