forked from nix-community/home-manager
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pull] master from nix-community:master #8
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The source uses `launcher` instead of `daemon`. Additionally we remove `Type` and add `RestartSec` as defined in the source: https://github.com/espanso/espanso/blob/b421bcf73fa13506938d62425459d6c16c6a8d0a/espanso/src/res/linux/systemd.service#L5-L7C1
When zoxide initializes after fzf it causes fzf " ** " trigger to not work. To fix the issue we needed to make zoxide initialize earlier than fzf but after bash-completion. PR #5955
Flake lock file updates: • Updated input 'nixpkgs': 'github:NixOS/nixpkgs/a3c0b3b21515f74fd2665903d4ce6bc4dc81c77c?narHash=sha256-nsNdSldaAyu6PE3YUA%2BYQLqUDJh%2BgRbBooMMekZJwvI%3D' (2024-10-14) → 'github:NixOS/nixpkgs/4c2fcb090b1f3e5b47eaa7bd33913b574a11e0a0?narHash=sha256-/uilDXvCIEs3C9l73JTACm4quuHUsIHcns1c%2BcHUJwA%3D' (2024-10-18) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
The `.assume-wrapped` path is not available since the merge of NixOS/nixpkgs#347816 Use assume directly instead. PR #5994
Actions were added in the v0.19.1 release.
This module enables wrapping programs which require access to libGL with nixGL on non-NixOS systems.
Some desktop files will refer to the absolute path of the original derivation, which would bypass nixGL wrapping. So we need to replace the path with the path to the wrapper derivation to ensure the wrapped version is always launched.
makeWrapper is more consistent with the rest of nixpkgs & home-manager, so it should be a little more maintainable. It can also validate that the wrapper command is executable at build time.
Co-authored-by: V. <[email protected]>
Co-authored-by: V. <[email protected]>
Co-authored-by: V. <[email protected]>
Previously, - `programs.yazi.enableNushellIntegration`, - `programs.yazi.enableFishIntegration`, and - `programs.yazi.enableZshIntegration` were set to false by default. It seems more appropriate to enable these integrations by default.
There's no launchd equivalent to this option, so this is a no-op on Darwin.
This facilitates a legitimate use-case for browserless systems. From the README: > On systems without a web browser, set the -device flag to authenticate > on another device using [OAuth device flow]: > ```ini [credential] helper = cache --timeout 7200 # two hours helper = oauth -device ``` [OAuth device flow]: https://www.rfc-editor.org/rfc/rfc8628 Please note that, for the documentation about the man-page to be accurate, NixOS/nixpkgs#302922 must be merged.
The initExtra code is executed after systemd graphical-session.target starts, which means graphical applications started by graphical-session.target cannot get these X settings.
The initExtra code is executed after systemd graphical-session.target starts, which means graphical applications started by graphical-session.target cannot get these X settings.
Now accepts an empty list, which turns off the code so the user can manually set ZSH_AUTOSUGGEST_STRATEGY anywhere they want via any of the `*Variables` module options.
The example for settingsPerApplication is missing a semicolon.
Some fish plugins such as https://github.com/acomagu/fish-async-prompt require that starship be initialized as non-interactive. When the `programs.starship.enableInteractive` option is enabled, starship is initialized at the end of the init script, outside the interactive block.
Changed the initialization method from `eval` to `source` as per the starship installation guide. See: https://starship.rs/guide/#%F0%9F%9A%80-installation This is in accordance with the Fish docs which recommends using `source` if the command does not need access to stdin, which in this case is what upstream has. See: https://fishshell.com/docs/current/cmds/eval.html
Including some useful presetting for notmuch and mbsync.
* mbsync: Add NEWS entry about isync 1.5.0 changes * mbsync: Place config file in $XDG_CONFIG_HOME mbsync 1.5.0 supports placing isync's configuration file in $XDG_CONFIG_HOME/isyncrc [1]. [1] https://sourceforge.net/projects/isync/files/isync/1.5.0/ * mbsync: Replace SSLType with TLSType mbsync 1.5.0 replaced the name of the configuration option [1]. Also update SSLVersions to TLSVersions for the same reason. Inform the user if the option was renamed. [1] https://sourceforge.net/projects/isync/files/isync/1.5.0/ * mbsync: Replace SSLVersions with TLSVerisons * mbsync: Update extraConfig.account example with SSL->TLS changes
Previously, only the main identity of an account would get the proper SMTP server assigned. Identities corresponding to aliases would not get an SMTP server assigned at all, leading to a (Thunderbird-internal) fallback to the SMTP server associated to the primary account. This is obviously wrong for non-primary accounts having aliases associated to them. Fix it by specifying the SMTP server explicitly for all identities.
Autin looks for the XDG_DATA_HOME which may not be set as $HOME/.local/share so lets use the systemd specifier for it instead.
The path is changing in 18.4.0 to XDG_RUNTIME_DIR over XDG_DATA_DIR so update the specifier. See atuinsh/atuin#2171.
When the version of Nushell or any Nushell plugin changes, the plugin registry must be regenerated.
D-Bus services are queried from Home Manager packages too. NixOS is not required.
The home manager script fails when $USER contains special characters. For example, my work PC is managed by company's LDAP and username is <COMPANY>\<user>). When running home-manager switch I get the following error: ``` error: flake 'path:/home/<COMPANY>/<user>/.config/home-manager' does not provide attribute 'packages.x86_64-linux.homeConfigurations."<COMPANY>\<user>".activationPackage', 'legacyPackages.x86_64-linux.homeConfigurations."<COMPANY>\<user>".activationPackage' or 'homeConfigurations."<COMPANY>\<user>".activationPackage' Did you mean <COMPANY><user>? ``` There are two types of strings that need escaping: strings in Nix expressions (e.g. home.nix generated by home-manager init) they need backslashes before special chars flake URI (passed to nix build) they need URI's percent encoding, luckily jq supports that
would fail on tests
Else I get a === … while calling the 'throw' builtin at /nix/store/afpmddfrmx5df3h16bdh00yy8i7db8w4-source/pkgs/desktops/gnome/default.nix:96:28: 95| gnome-shell = throw "The ‘gnome.gnome-shell’ was moved to top-level. Please use ‘pkgs.gnome-shell’ directly."; # Added on 2024-08-28. 96| gnome-shell-extensions = throw "The ‘gnome.gnome-shell-extensions’ was moved to top-level. Please use ‘pkgs.gnome-shell-extensions’ directly."; # Added on 2024-08-11. | ^ 97| gnome-software = throw "The ‘gnome.gnome-software’ was moved to top-level. Please use ‘pkgs.gnome-software’ directly."; # Added on 2024-08-11. error: The ‘gnome.gnome-shell-extensions’ was moved to top-level. Please use ‘pkgs.gnome-shell-extensions’ directly. === on rebuild
Makes it so settings.json no longer gets made by ensuring it can be empty as expected when there are no extensions or userSettings defined. PR #6201
Similar to what we did for firefox for darwin support.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )