remove "redundant" config from script?

[michaelzoech]

maybe we should put the complete call to dmenu with params into exactly one property for the user to configure in the config file.

pros:

• remove unnecessary properties from script.
• remove dependency from dmenu. user could use any app he wants to pick buddy to chat with.
• call will be scriptable, e.g. i could write a script for positioning the dmenu based on current display resolution.

[anpieber]

mhm, this sounds quite nice; additionally it will reduce the required code in the script immense :)

to write scripts about the positioning maybe it will help to be able to put all configurations per commend line to the script? WDYT?

I set this issue as a task for the next release!

[michaelzoech]

what do you mean exactly with "put all configurations per command line to the script" ? do you mean that it should be possible to configure the script from config file and command line too?

[anpieber]

yep; i think this will be nice. I think about something like -config.NAME VALUE

configuration given via cmd is only value for one run;but this allows you to configure the tools via scripts. I think of this very handy in case of using some windowmanagers such as ratpoison where you can bound entire, very complex scripts to short keys

[michaelzoech]

+1

-config.NAME VALUE is ok, but what about the more *nix way of --NAME=VALUE ?

[anpieber]

+1; but would also add this to pyimc-0.2.0 and release the pyimc-0.1.0 now :)

[michaelzoech]

this issue should remove the required dmenu-vertical dependency, update PKGBUILD accordingly

[anpieber]

created own issue for dmenu-vertical reference

[michaelzoech]

done