Hi, I just thought I could do something meaningful while reading that dusty coding style stuff.
So I started with #532383 as it seemed nobody touched this yet. If any of you can assist, my ears are open as this is my first package (not yet). I attached a first draft for debian/control and will read further on compat next. #532383 please provide a -dbg package < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532383 > there is not dbg build of awesome > (and I don't have the time to rebuild it right now). So please > provide a -dbg package. Does it make sense to create a new doc or is it overhead for this size? If this is usal practice is there an example where I can see how to do this easily? #546688 Split luadoc into a new package < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546688 > It would be good to have /usr/share/doc/awesome/luadoc split into a > new package (saving 668K of disk space). > I know that 668K is nothing by today's standards, but having the > option to install it or not is a good idea. If any of you wants to pick one of the smaller ones below, please give a short ping, so we do not interfere. Although I will not touch them until i finished the others above and the config abstraction. Kardan RELATED TO CONFIG ----------------- #526909 "awesome -k" should also parse the theme file < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526909 > Today I saw a dead awesome here. Nothing working, no taskbar, nothing. > "awesome -k" was giving "Configuration file syntax OK." but then I > saw this on .xsession-errors: > /home/naoliv/.config/awesome/theme.lua:5: unexpected symbol near '8' > I saw that the syntax has changed, but "awesome -k" should also > verify my theme file or awesome should somehow use a default theme, > if the specified one is broken. #529642 awesome is not customizable, aka upgrading is a PITA < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529642 > There hasn't been an upgrade between minor versions (3.x->3.y) where > I had to change my configuration *again*, because something changed > in awesome. > The problem is that awesome currently lacks higher > configuration interface, and by this, forces users to deal directly > the still unstable API. > Even if awful is getting more and more easy to use, having > something higher level would be nice for (some) users. POTENTIALLY EASY TO FIX ----------------------- #573302 awesome should create an application entry < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573302 > awesome doesn't install an application entry (a .desktop entry in > /usr/share/applications) and I think it should, to let you easily > replace the GNOME window manager. See /usr/bin/gnome-wm comment > (talking about other methods to change the WM): > # NOTE: DON'T USE THIS. Please have your window manager install > # a desktop file and change the gconf key > # /desktop/gnome/session/required_components/windowmanager #600995 55awesome-javaworkaround: There should be x-window-manager < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600995 > There is x-session-manager in that file. > There is _no_ x-session-manager in my /etc/alternatives folder. > I've manualy changed the x-session/manager to x-window-manager and it > works. > Probably it is a good idea to add at least one more line: > AWT_TOOLKIT=MToolkit; export AWT_TOOLKIT > for users that for some reason _must_/want to use sun-jdk #600429 default menu option "manual" don't open the awesome manual < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600429 > patch is applied to add quotes for exec "terminal -e man awesome" > bug is tagged moreinfo with no response since 9 Dec 2011 #527115 mention dofile("/etc/xdg/awesome/rc.lua") in awesomerc man page < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527115 > In the awesomerc man page, it would be nice if it suggested creating > ~/.config/awesome/rc.lua with an initial line containing > dofile("/etc/xdg/awesome/rc.lua") > or some other mechanism to allow using the default configuration > (including updates when they happen), with additional customizations > in the user's rc.lua. > The problem with that one is that some actions will be repeated as > the initialization is not split from the variable settings #693135 menu should include xdg desktop entries < http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693135 > I wish, awesome would not (only) use the debian menu but show > application menu entries as specified by the freedesktop menu > specification[1]. > [1] http://standards.freedesktop.org/menu-spec/latest > Thus awesome would somehow need to parse desktop entry files from > /usr/share/applications. I saw two scripts for this on the net: > https://github.com/chouilleur/xdg-menu-to-awesome-wm > https://wiki.archlinux.org/index.php/Xdg-menu#Awesome
control
Description: Binary data
