Here are some suggestions I have, mainly regarding ext_statusbar: -- Mark ourselves loaded. _LOADED["mod_menu"]=true
at the bottom of "ext_statusbar.lua" should probably read: -- Mark ourselves loaded. _LOADED["ext_statusbar"]=true I also think that all of the code currently in ext_statusbar.lua for registering specific meters and the corresponding functions should be moved to cfg_statusbar.lua. Finally, I think cfg_statusbar.lua should load ext_statusbar.lua rather than ext_statusbar.lua loading cfg_statusbar.lua; I think such organization is more suitable for a library. Regarding the recent inclusion of documentation directives for each of the key bindings, I find this litters the config files will a lot of unnecessary text; if Lua supports it, I would suggest instead that the documentation strings be bound to the underlying functions rather than the key bindings -- this is what Emacs does, for example. -- Jeremy Maitin-Shepard
pgpeBwnA8v4UV.pgp
Description: PGP signature
