[dev] Tabbed + Surf, possible bug on closing tab

2010-07-25 Thread Martin Kopta
Hi everybody, I use Tabbed (0.3) with Surf (0.4.1) and there is one issue I would like to discuss. Situation: Tabbed is running with few Surf instances within. I intend to close ONE Surf instance. I use ^q or middle click (emulated using left+right) on tab name. Results: I expect that

Re: [dev] Tabbed + Surf, possible bug on closing tab

2010-07-25 Thread Troels Henriksen
Martin Kopta writes: > Hi everybody, > > I use Tabbed (0.3) with Surf (0.4.1) and there is one issue I would like to > discuss. > > Situation: > > Tabbed is running with few Surf instances within. I intend to close ONE Surf > instance. I use ^q or middle click (emulated using left+right) on

Re: [dev] dwm: XineramaQueryScreens() is called twice in updategeom()

2010-07-25 Thread Anselm R Garbe
Hi Hiltjo, On 24 July 2010 18:30, Hiltjo Posthuma wrote: > I checked dwm with valgrind, just to see if it showed up anything > interesting. I saw in the "updategeom" function Xinerama is queried twice > when Xinerama is enabled. I attached a patch which fixes this. Thanks a lot for this. That mu

Re: [dev] Tabbed + Surf, possible bug on closing tab

2010-07-25 Thread Rob
On 25 July 2010 09:47, Troels Henriksen wrote: > Martin Kopta writes: > >> Hi everybody, >> >>   I use Tabbed (0.3) with Surf (0.4.1) and there is one issue I would like to >> discuss. ... >>   I expect that the selected one window (tab) will be closed. In most cases >> it >>   is exactly so, bu

[dev] [surf] leak and segfault patches

2010-07-25 Thread Rob
Hi, I found a few problems when I was messing around with surf this afternoon. The first patch should fix a memory leak that happens when surf loads a new uri. I tried to check with debug flags and valgrind, but, after sifting through the usual thousand or so GTK leaks, invalid writes and other as

Re: [dev] [surf] leak and segfault patches

2010-07-25 Thread Kris Maglione
On Sun, Jul 25, 2010 at 03:50:59PM +0100, Rob wrote: Hi, I found a few problems when I was messing around with surf this afternoon. The first patch should fix a memory leak that happens when surf loads a new uri. I tried to check with debug flags and valgrind, but, after sifting through the usua