awesome

Welcome to awesome bug tracking system.
Tasklist

FS#668 - Simplify merging of 'common' rc.lua customizations into new awesome releases

Attached to Project: awesome
Opened by Roger Gallion (noillagr) - Saturday, 24 October 2009, 11:27 GMT
Task Type Evolution Request
Category Core
Status Unconfirmed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version 3.4
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

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.
This task depends upon

Comment by Pawe? Zuzelski (pawelz) - Monday, 26 October 2009, 00:06 GMT
In my opinion it would have been much easier to merge changes if rc.lua was split into a few files.
It is easier to merge changes to few small files than one big file. Moreover API changes are quite small in recent releases, so the probability that all files needs to be adapted to new releases is small.
Comment by Risto Varanka (varis) - Tuesday, 12 April 2011, 22:48 GMT
One solution could be providing alternate configuration files with Awesome. I think this could be tried for 3.4.10. User feedback needs to be collected about which configuration sets would be desired (nobody wants to start customizing from a config with *all* possible customizations).

Loading...