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

polybar: allow config to be more nix-like #1430

Merged
merged 1 commit into from
Feb 20, 2021

Conversation

Nadrieril
Copy link
Contributor

@Nadrieril Nadrieril commented Aug 7, 2020

Description

Polybar's config format is a bit strange, and lists in particular are annoying to handle. This enables using normal nix lists and nested attrsets instead.

I had to create a new option because this change would not be backwards-compatible, because the INI converter currently converts lists of strings to space-separated values, and this new option does something else. I expect that this is only relevant for the modules-left etc bar setting, but that's enough to break things :(.

I'm not sure how to name this new option. I named it settings because I thought we might decide to deprecate config in its favor later.

Checklist

  • Change is backwards compatible.

  • Code formatted with ./format.

  • Code tested through nix-shell --pure tests -A run.all.

  • Test cases updated/added. See example.

  • Commit messages are formatted like

    {component}: {description}
    
    {long description}
    

    See CONTRIBUTING for more information and recent commit messages for examples.

@Nadrieril Nadrieril requested a review from rycee as a code owner August 7, 2020 17:30
@Nadrieril
Copy link
Contributor Author

Bump

@teto
Copy link
Collaborator

teto commented Feb 20, 2021

ok can you rebase please ?

@Nadrieril
Copy link
Contributor Author

Done

Polybar's config format is a bit strange, and lists in particular are
annoying to handle. This enables using normal nix lists and nested
attrsets instead.

This change is not backwards-compatible, because the INI converter
converts lists of strings to space-separated values, and this does
something else. I expect that this is only relevant for the
`modules-left` etc bar setting, but that's enough to break things :(.
@teto teto merged commit da92360 into nix-community:master Feb 20, 2021
@Nadrieril Nadrieril deleted the polybar-config branch February 20, 2021 17:58
malte-v pushed a commit to malte-v/home-manager that referenced this pull request Feb 24, 2021
Polybar's config format is a bit strange, and lists in particular are
annoying to handle. This enables using normal nix lists and nested
attrsets instead.

This change is not backwards-compatible, because the INI converter
converts lists of strings to space-separated values, and this does
something else. I expect that this is only relevant for the
`modules-left` etc bar setting, but that's enough to break things :(.
aakropotkin pushed a commit to aakropotkin/home-manager that referenced this pull request Feb 28, 2021
Polybar's config format is a bit strange, and lists in particular are
annoying to handle. This enables using normal nix lists and nested
attrsets instead.

This change is not backwards-compatible, because the INI converter
converts lists of strings to space-separated values, and this does
something else. I expect that this is only relevant for the
`modules-left` etc bar setting, but that's enough to break things :(.
cab404 pushed a commit to cab404/home-manager that referenced this pull request Apr 23, 2021
Polybar's config format is a bit strange, and lists in particular are
annoying to handle. This enables using normal nix lists and nested
attrsets instead.

This change is not backwards-compatible, because the INI converter
converts lists of strings to space-separated values, and this does
something else. I expect that this is only relevant for the
`modules-left` etc bar setting, but that's enough to break things :(.
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

Successfully merging this pull request may close these issues.

2 participants