Re: [dev] interested in issue tracker dev
2012/1/12 markus schnalke mei...@marmaro.de [2012-01-12 19:06] Anselm R Garbe garb...@gmail.com On 12 January 2012 18:34, aecepo...@gmail.com wrote: I might be interested in trying to help write one such suckless issue tracker as requested on the webpage. I just want to ask; What set of features are a must for you? Oh what a relief someone wants to volunteer on this idea. One of the most important things of such a tracker is decent mail integration in my opinion (as most trackers that have evolved in the OSS space recently suck very much when it comes to mail integration). What about roundup - http://roundup.sourceforge.net ? I don't use it myself but it was already adopted by some major teams like the mercurial crew for example. However, It's also very handy to be able to download issue history in a mbox format as bugzilla does (in case you're not subscribed) but I'm not sure it's possible in roundup configuration. Regards,
Re: [dev] wmii how to replace status bar with dzen2
2011/2/7 Michael mlmichae...@gmail.com:
On 07/02/2011 10:19, Thomas Dahms wrote:
I don't see the point in using a third-party status bar with wmii, you
(...)
Probably I could get away with text info instead of icons, but then I still
need some way of changing the color of given text depending on it's value.
And I failed to find a way of doing it in wmiirc.
I had similar needs in the past and wrote some stuff that can help you
a bit to write your wmii applets:
https://bitbucket.org/juj/wmii/src/tip/rbar/
To enable your right bar, you can adapt this snippet in your wmiirc:
echo | wmiir create /rbar/ # left separator
for bar in $WMII_PATH/rbar/*(x); {
if wmiir remove /rbar/$bar 2/dev/null; then
killall $bar:t /dev/null
fi
PATH=$WMII_PATH/rbar:$PATH nice -n 19 $bar
}
It uses zsh but it should be easy to translate/improve to (ba)sh
syntax. The only problem is the number of processes (but most of the
time in sleep state).
This solution works not so bad but if you want to create a full
graphics bar I recommend you to switch to the combo: conky (cli) +
dzen2. Nevertheless in wmii, I prefer to manage my left bar (views) by
wmii events directly.
Hope it can help,
--
J u l i e n J e h a n n e t
Re: [dev] what program to create custom menus
* Michael mlmichae...@gmail.com [28-janv.-2011 16:26]: Hello. What program do you recommend to create a pop-up menu with a list of my favorite applications in wmii? I mean: I hit MOD1+SHIFT+P and menu pops up with a list of categories like: multimedia, internet. When I choose (with arrow keys) internet then sub menu pops up with a list of applications like: firefox, thunderbird. When I choose one of them (with enter key) then it gets executed. Have you tried dzen2 ? http://dzen.geekmode.org/dwiki/lib/exe/fetch.php?media=dzen:dzen_menu_shot.png I found a tutorial here: https://bbs.archlinux.org/viewtopic.php?pid=390680 Nevertheless, I'm not sure you can easily navigate from keyboard easily. But give it a try and let us know :-) -- N e h u m a n u s c r e d e signature.asc Description: Digital signature
Re: [dev] wmii - how to put bar on top
2011/1/15 Michal Hajek haj...@karlov.mff.cuni.cz: I am using wmii and now I need to place bar on top instead of bottom of my screen. How do I do that? It depends on your wmii version but try: wmiir xwrite /ctl bar on top Or just give a second change to the project homepage... http://hg.suckless.org/wmii/raw-file/tip/doc/wmii.pdf Archival wmii documentation Here, for archival purposes, are the guides to historical releases of wmii. They have been superseded by doc/wmii.pdf in the standard distribution. URL: http://hg.suckless.org/wmii/raw-file/tip/doc/wmii.pdf Yes, text could be more visible indeed. Best regards,
Re: [dev] git dmenu mirror with feature branches instead of separate patches
2010/11/22 Anselm R Garbe garb...@gmail.com: I don't mind if you set up a git repo where each patch from the website resides in a separate branch, but I think you just organise the existing approach just differently. You don't fix the problem, which is having a suitable process to determine the best feature set for the software by default. So far the patch based approach was good enough to count the downloads and to decide on popularity or necessity of some patches to be applied to the mainstream repo at some point. And everyone can easily add a patch file to the wiki, apart from having a central place for the patch files. Hello, Just to mention the possibility to record patches into hg patch repositories instead of the wiki. http://mercurial.selenic.com/wiki/MqTutorial#Indicate_that_you_want_to_use_mq_on_this_repository The advantage is to have a dedicated repo to clone and a possibility to select what patch to merge by editing series file (and there are more chances to update them this way). For example with a patch repo named dmenu-patches, you have to link this repo to dmenu/.hg/patches. But note this solution is not immediate since you have to set an alias (not sure but should be done directly in .hgrc with mercurial 1.7): alias mq='hg -R $(hg root)/.hg/patches' BW -- J u l i e n J e h a n n e t
