THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened. Details are below. User who did this - Roger Gallion (noillagr)
Attached to Project - awesome
Summary - Simplify merging of 'common' rc.lua customizations into new awesome 
releases
Task Type - Evolution Request
Category - Core
Status - Unconfirmed
Assigned To - Operating System - All
Severity - Low
Priority - Normal
Reported Version - 3.4
Due in Version - Undecided
Due Date - Undecided
Details - I love awesome, but merging personal rc.lua customizations into new 
releases is often too time-consuming.  Perhaps if developers were aware of 
common rc.lua customizations users make, then the situation would improve.  
Here is a short list of possible customizations:
- Having fewer than 9 tags per screen
- Reducing/re-ordering the 'layouts' table entries
- Having a user-defined default screen layout
- Having no main menu
- Having custom date/time format for the textclock widget
- Defining modkey-0 to cycle through screens
- Adding awful.key entries for special keys (volume/cd/etc.)
- Defining 'floating' apps
- Defining tag-specific apps

This request was trigger by the recent upgrade to awesome 3.4 on ArchLinux. It appears that the default layout for 3.4 is 'floating', but since floating was disabled in my rc.lua 'layouts' table, problems ensued. Investigation revealed that awful/layout/init.lua returns suit.floating if the layout property has not been defined for a screen tag. Modifying the init.lua file was undesirable. Considerable further investigation was required to discover that the awful.tag.new function has a 'layout' parameter to set the default layout for new screen tags. Unfortunately the rc.lua distributed with 3.4 does not set that parameter.

I would not wish to have rc.lua locked down, since it provides customizable 
access to new awesome functionality.  But every time my rc.lua customizations 
are broken by new awesome releases, I go investigate the state of other tiling 
window managers.  Perhaps I am not the only one to do so.

More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=details&task_id=668

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to [email protected].

Reply via email to