Configuration file

[Cloudef]

Add configuration file and move colors to there from the command line. Maybe some other options too that make sense. Add command line option for choosing different configuration file than default.

[Cloudef]

Maybe good reason to migrate inihck to use ragel, and then use that.

[Cloudef]

Main configuration files
/etc/bemenu/bemenu.ini, $XDG_CONFIG_HOME/bemenu/bemenu.ini

Program specific file
/etc/bemenu/bemenu-run.ini , $XDG_CONFIG_HOME/bemenu/bemenu-run.ini

Main configuration files are loaded first, then program specific file.
Global is loaded first, then local file.

Command line switches are applied last.
If --config switch is used, only that configuration file is loaded.

Add configuration key that can control the loading behaviour of program specific files.
never/local/default

[stacyharper]

This feature still is in the pipes ? I'd really like to have a configuration way. This is the really bad point of dmenu. Any news about this ?

[Cloudef]

No timeline for this. I've personally felt like bemenu fits all my needs already.

[Cloudef]

There is now configuration through BEMENU_OPTS env variable. It works similar to cli arguments.
E.g. BEMENU_OPTS='-p "foo bar" -fn Arial' bemenu-run

dac1ffd

[meMuszr]

Would you accept a PR for parsing configuration files?

[Cloudef]

Is there a reason you'd prefer configuration file over the BEMENU_OPTS env variable?

[PRESFIL]

The reason may be this.
There is a solution proposed, but it is ugly and it does not always work to adapt. I wanted to make a general colors for i3-dmenu-desktop, dmenu_recency and dmenu with setting colors from the i3wm config, but nothing happened. This may be unnecessary, but with the configuration file everything would be easier. dmenu-derivatives do not have config files at all.

[Cloudef]

I mean, unless you need "script specific" configuration, the BEMENU_OPTS is global if exported before launching i3wm.

[octvs]

Considering the clean structure under a dotfile repo, config file has a clear advantage compared to the clutter of the env variable on bashrc (or somewhere else). This might be the only tool I use in my wm, that requires non-dynamic configuration settings, at the same time not reading a config file.