| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Allow disabling channels
|
|
|
|
|
|
|
|
Use this and never find yourself again hitting fn because of muscle
memory! (you can even physically swap the keycaps, at least on M series)
Keycodes have been pulled from https://hidutil-generator.netlify.app/
and the hex value has been converted to a base 10 int.
|
|
system.defaults.windowmanager
All credits go to @AlexOwl. Their [PR](https://github.com/LnL7/nix-darwin/pull/505)
looked abandonned so I reported their changes and addressed the change
requests.
|
|
|
|
github-runners: move `workDir` outside of `/run`
|
|
defaults: only restart Dock when user is logged in
|
|
deprecated in https://github.com/NixOS/nixpkgs/commit/473e469d5a921a57b484a09d446cee6c231cd592
|
|
As `/run` gets recreated every reboot and we can't specify dependencies
for launchd, creating the `workDir` every reboot will require extra
complexity with a separate daemon that runs as `root` otherwise it won't
have sufficient privileges.
As we clean the `workDir` when the service first starts anyway, it ends
up being the same.
|
|
|
|
This reverts commit fe99aa9699e7dd4ce6a81a8a623d010cedbe7eef.
|
|
|
|
|
|
|
|
|
|
module : `jankyborders` for window borders Configuration
|
|
- Added the jankyborders service.
- Introduced changes for whitelist and blacklist options and assertions.
- emoved path reference from launchd argument.
- Corrected missing trailing newline in default.nix.
|
|
defaults: restart Dock when changing settings
|
|
|
|
Add `User` and already generated `IdentityFile` to ssh_config for `nix.linux-builder`
|
|
Co-authored-by: Michael Hoang <Enzime@users.noreply.github.com>
|
|
ssh: use symlinks for `authorizedKeys` options
|
|
`nix.linux-builder`
|
|
|
|
|
|
|
|
|
|
|
|
Before this commit, aarch64 users building the following configuration
would end up with an aarch64-linux builder, while after it, they get the
x86_64-linux builder they expect:
```nix
nix.linux-builder = {
enable = true;
package = pkgs.darwin.linux-builder-x86_64;
};
```
Before, in order to get an x86_64-linux builder, they would have needed
to use this configuration instead:
```nix
nix.linux-builder = {
enable = true;
config.nixpkgs.hostPlatform = "x86_64-linux";
systems = ["x86_64-linux"];
};
```
The reason for this is that the linux-builder module calls `override` on
the package option, and the `linux-builder-x86_64` package is also
defined using override:
```nix
linux-builder-x86_64 = linux-builder.override {
modules = [ { nixpkgs.hostPlatform = "x86_64-linux"; } ];
};
```
The module was effectively discarding the `nixpkgs.hostPlatform` option.
Example issue: https://github.com/NixOS/nixpkgs/issues/313784
|
|
This is a huge anti‐declarative footgun; `copy` files cannot
distinguish if a previous version is managed by nix-darwin, so they
can’t check the hash, so they’re prone to destroying data, and
copied files are not deleted when they’re removed from the system
configuration, which led to a security bug. Nothing else in‐tree
was using this functionality, so let’s make sure it doesn’t
cause any more bugs.
|
|
As explained in the changelog and activation check, the previous
implementation had a nasty security bug that made removing a user’s
authorized keys effectively a no‐op.
|
|
fix(launchd): improve `StartCalendarInterval`
|
|
fonts: reimplement and rename to `fonts.packages`
|
|
Drop compatibility for unsupported Nixpkgs versions
|
|
linux-builder: remove trusted user requirement
|
|
All supported Nixpkgs versions now support this.
This reverts commit a5b09580e2d0bbc52b338afe4f1f1d46178e6bbf.
|
|
These deprecated versions were already made unsupported by #932.
|
|
As far as I can tell, this isn't required to get fonts to work on
NixOS, so we shouldn't require it on nix-darwin either, even if the
implementations are superficially similar.
|
|
Fixes: #120
Fixes: #722
Fixes: #752
Closes: #692
|
|
Process substitution behaves better with variables and it's good
practice to use `lib.escapeShellArgs`.
|
|
|
|
launchd: add LowPriorityBackgroundIO config
|
|
Stricter launchd -> StartCalendarInterval type:
- Verify that the integers passed to `Minute`, `Hour`, etc. are within
range.
- When provided, the value for StartCalendarInterval must be a non-empty
list of calendar intervals and must not contain duplicates entries
(throw an error otherwise).
- For increased flexibility and backwards-compatibility, allow an
attrset to be passed as well (which will be type-checked and is
functionally equivalent to passing a singleton list). Allowing an
attrset or list is precisely in-line with what `launchd.plist(5)`
accepts for StartCalendarInterval.
Migrate `nix.gc.interval` and `nix.optimise.interval` over to use this
new type, and update their defaults to run weekly instead of daily.
Create `modules/launchd/types.nix` file for easier/modular use of
launchd types needed in multiple files.
Documentation:
- Update and improve wording/documentation of launchd's
`StartCalendarInterval`.
- Improve wording/documentation of `nix.gc.interval` and
`nix.optimise.interval` ("time interval" can be misleading as it's
actually a "calendar interval"; e.g. `{ Hour = 3; Minute = 15;}`
runs daily, not every 3.25 hours).
|
|
|
|
|
|
Add support for trackpad force click
|
|
Co-authored-by: Michael Hoang <Enzime@users.noreply.github.com>
|
