Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config files needed for customizing dmenu #42

Closed
ghost opened this issue Nov 6, 2021 · 2 comments
Closed

Config files needed for customizing dmenu #42

ghost opened this issue Nov 6, 2021 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 6, 2021

Please make the dmenu customizable using config files in ~/.config/dmenu

Preferably toml or yml file.

@Shizcow
Copy link
Owner

Shizcow commented Nov 6, 2021

I've thought about this one a lot. The only way I'd implement config files is if I also revamped the plug-in system. I want to do this, but won't have time in my life for quite a while.

Some ideas/desired features on this topic:

  • ability to set default font / colors / etc
  • ability to add default parameters to the command (as a fallback)
  • ability to modify top / bottom / other already supported UI options

As for how plugins can interact:

  • remove the compile time step, allowing this to be shipped with cargo install
  • have plugins look in 3 locations during startup:
    • system package / run path. This way, in theory, you could install dmenu-rs plugins via your system package manager. Same as how arch handles python packages
    • .cargo: so plugins could be installed via cargo install
    • .config/dmenu: manual installation and plugins in development
  • Alternatively / in addition to, plugins may need to be registered before use so they're not automatically loaded in (speed?)
  • plugins can provide toml configuration keys available to modify in the main config file

Other ideas welcome

@Shizcow
Copy link
Owner

Shizcow commented Aug 9, 2023

New plugin system won't ever happen without rust-lang/rfcs#1880. I've been waiting on this for a few years and it doesn't look like it's going to happen any time soon. So unfortunately closing this as wontfix.

@Shizcow Shizcow closed this as completed Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant