-
Notifications
You must be signed in to change notification settings - Fork 139
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
Proposal: modes #335
Comments
Ooh, I like this proposal, especially with #306. This seems much simpler to both use and implement without confusion w.r.t. merging contexts. The only issue I imagine is that with #138, you can dynamically generate everything on-the-fly, while this proposal requires hard coding all possible values. However, because |
I think this is the right path forward. It also doesn't preclude adding |
I think this is a main reason I like this proposal. It has no conflicts with |
Side note: I can see how allowing multiple modes active at the same time could be useful, but I'm not sure it's something we want. |
I don't think there's a need to do it right now either, and in the future we could have |
I've implemented this in #362. Please try it out! |
Works well for me, thank you for implementing it! |
When I try |
This is a counter-proposal for #138.
Instead of allowing to change arbitrary configuration options, we could introduce modes:
Modes could be switched at runtime with e.g.
makoctl set-mode dnd
. There is only one mode active at a time.The text was updated successfully, but these errors were encountered: