-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gregor Best wrote:
Thanks, merged (finally) :)
/me gives Gregor a cookie
- --
Do you know that books smell like nutmeg or some spice from a foreign land?
-- Faber in Fahrenheit 451
-BEGIN PGP
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Florian Friesdorf (chaoflow)
Attached to Project - awesome
Summary - windows get killed
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#585 - windows get killed
User who did this - Uli Schlachter (psychon)
--
You can try adding print(test) (should write to stdout, I think) or
io.stderr:write(test\n) to your rc.lua to generate
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#585 - windows get killed
User who did this - Uli Schlachter (psychon)
--
Can you try with xterm's -hold option? (Do not close the xterm if the shell
running in xterm dies)
I doubt that it will
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#585 - windows get killed
User who did this - Gregor Best (farhaven)
--
Also, could you paste the output of dmesg (at least the last 20 - 30 lines)?
Maybe the clients segfault or something, which
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#585 - windows get killed
User who did this - Florian Friesdorf (chaoflow)
--
I am pretty sure, not really sure, that now the xterm died in which offlineimap
was running.
dmesg reveals the
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#585 - windows get killed
User who did this - Uli Schlachter (psychon)
--
Those messages come from BUG() or BUG_ON() calls in the linux kernel source.
I'd say your kernel kind-of oops'd while it
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#585 - windows get killed
User who did this - Gregor Best (farhaven)
--
Hmm, looks like a hardware issue, though I'm not quite sure how awesome could
play into this, as it seems to be the only wm
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Julien Danjou (jd)
Attached to Project - awesome
Summary - Use screen object rather than integer
Task Type - Evolution Request
Category - Core
Status - New
Assigned To -
This seems to duplicate the unpolished tho fully functional awful.doc
that I was working on a while back, before stuff ranging from my
laptop to master branch started breaking.
The module provides more generic means of describing clients (among
other objects) and it would be pretty trivial to
Hmm, if that's the case, then I'm against merging my patch. I'd prefer
konius stuff, because what I've seen on a few screenshots some time ago
was really impressive.
--
GCS/IT/M d- s+:- a-- C++ UL+++ US UB++ P+++ L+++ E--- W+ N+ o--
K- w--- ?O M-- ?V PS++ PE- Y++ PGP+++ t+ 5 X+ R tv b+++ DI+++
Before this brief rant, note that my experience with xmonad lasted
less than half an hour, and my knowledge of Haskell is non existent,
however..
AFAIK lua is amongst the fastest scripting languages, not sure how it
compares with Haskell though, would be interested in seeing some
benchmarks.
The
On Tue, Aug 18, 2009 at 5:58 PM, James Pearsonxiong.chiam...@gmail.com wrote:
On Tue, Aug 18, 2009 at 8:37 AM, Jochen Schulz m...@well-adjusted.de wrote:
Julien Danjou:
I've published the results here[1] and wrote some analyzes too. You're
free to redo it yourself if do not trust me. :-)
Excerpts from Ramon Diaz-Uriarte's message of Tue Aug 18 14:02:47 -0400 2009:
On Tue, Aug 18, 2009 at 5:58 PM, James Pearsonxiong.chiam...@gmail.com
wrote:
On Tue, Aug 18, 2009 at 8:37 AM, Jochen Schulz m...@well-adjusted.de
wrote:
Julien Danjou:
I've published the results
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#585 - windows get killed
User who did this - Byron Clark (byronc)
--
I'm seeing the same issue, minus the kernel WARNING.
[68613.825138] xterm[3325]: segfault at 10095d4f2 ip 004304f0 sp
In the last few weeks, I've had a number of segmentation faults related to wicd
(wireless manager) with Awesome 3.3.1. It's not reproducable, except that it is
connected to the tray icon. sometimes it will crash when hovering the icon,
sometimes when clicking it. note that it also may work
From: Fabienne Ducroquet fabi...@gmail.com
Date: Mon, 17 Aug 2009 22:21:25 +0200
Signed-off-by: Fabienne Ducroquet fabi...@gmail.com
---
On Mon, 17 Aug 2009 11:42:09 +0200, Tanguy Ortolo
tanguy+awes...@ortolo.eu wrote:
As maybe every french awesome user, I had to redefine the upper row key
17 matches
Mail list logo
