At 1239236186 time_t, koniu wrote:
I was wondering if there's a strong reason for having the hardcoded
bit forcing default tag to be created if there are no tags in the
screen. I think that this should be left to lua side - with the
current default rc.lua never even touching the problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
koniu wrote:
Hi,
I was wondering if there's a strong reason for having the hardcoded
bit forcing default tag to be created if there are no tags in the
screen. I think that this should be left to lua side - with the
current default rc.lua never
Hi,
if you restart awesome and the rc.lua doesnt create any tags at all, what
happens? When I was using shifty I used to lose a couple of windows across
awesome restart. They just disappeared, but the app was still running.
If rc.lua doesn't create tags when awesome is restarted, by default,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
koniu wrote:
Hi,
if you restart awesome and the rc.lua doesnt create any tags at all, what
happens? When I was using shifty I used to lose a couple of windows across
awesome restart. They just disappeared, but the app was still running.
If
Hi,
I was wondering if there's a strong reason for having the hardcoded
bit forcing default tag to be created if there are no tags in the
screen. I think that this should be left to lua side - with the
current default rc.lua never even touching the problem (static tags)
and users/libraries (like
