[Xmonad] mod-shift-c has no effect
Donald Bruce Stewart
dons at cse.unsw.edu.au
Sun Apr 15 18:59:40 EDT 2007
> On Sun, Apr 15, 2007 at 10:51:37PM +0200, Georg Neis wrote:
> > dons at cse.unsw.edu.au (Donald Bruce Stewart) wrote:
> > > gn:
> > > > Georg Neis <gn at oglaroon.de> wrote:
> > > > > the only program that I'm able to kill by pressing mod-shift-c is
> > > > > xterm. For all other programs I can't notice any effect.
> > > >
> > > > I've found the reason. In my .xinitrc I used to start the tool
> > > > root-tail to print some logfile to the root window. If I comment out
> > > > that line, then mod-shift-c works as expected. I don't know why. I
> > > > also wonder why manually running root-tail from an xterm after xmonad
> > > > has started up doesn't cause any trouble.
> > > >
> > >
> > > Ok. This is a bit wierd. Can you narrow it down any further?
> > I've no idea what to look at. Can anyone reproduce this at least?
> > I can say, however, that I don't have this issue when using dwm.
> I don't know what root-tail is, but I can confirm that mod-shift-c doesn't
> kill xclocks for me, but does kill xterms (but not aterms). No idea what
> that means, and I haven't much time (or motivation) to track it down,
> although it is annoying.
Ok. I can reproduce this with xclock. I'll track it down later this
week. Most likely there were some assumptions (in the slightly dodgy)
send destroy event code in X11-extras, that broke somewhere.
More information about the Xmonad