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

Refactor new-lines in i3-config like done for sway #2030

Open
SebTM opened this issue May 20, 2021 · 3 comments
Open

Refactor new-lines in i3-config like done for sway #2030

SebTM opened this issue May 20, 2021 · 3 comments
Labels
pinned Prevent marking as stale

Comments

@SebTM
Copy link
Collaborator

SebTM commented May 20, 2021

Issue description

As discussed in #2003 we should change the config-generation for i3 according to sway to not have random newlines if options are not set and get rid of trailing spaces. I already started working on that. (https://github.com/SebTM/home-manager/tree/i3-refactoring)

Meta

Maintainer CC

@sumnerevans
@alexarice

@sumnerevans
Copy link
Member

we should also fix any functions in lib/functions.nix (barStr for example). See #2135 for an example of why

@stale
Copy link

stale bot commented Sep 21, 2021

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

  • If this is resolved, please consider closing it so that the maintainers know not to focus on this.
  • If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

  • If you are also experiencing this issue, please add details of your situation to help with the debugging process.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.

Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

@stale stale bot added the status: stale label Sep 21, 2021
@sumnerevans sumnerevans added the pinned Prevent marking as stale label Sep 22, 2021
@stale stale bot removed the status: stale label Sep 22, 2021
@sumnerevans
Copy link
Member

This is being worked on. Marked as pinned. I just have to get around to reviewing the corresponding PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pinned Prevent marking as stale
Projects
None yet
Development

No branches or pull requests

2 participants