Zed uses JSON5 for settings files. JQ doesn't understand that format and
fails if found, when merging with preexisting settings.
Here I add a conversion step that converts JSON5 to JSON before handling
the contents to JQ.
Besides, I changed the arguments in the jq function, so instead of using
`[0]` and `[1]`, we now use `$dynamic` and `$static` respectively. This
should make scripts more readable.
Fixes https://github.com/nix-community/home-manager/issues/7247
Fixes https://github.com/nix-community/home-manager/issues/7226
Reduce maintenance burden and increase efficiency by automatically
importing modules following a specific convention.
Co-authored-by: awwpotato <awwpotato@voidq.com>
Signed-off-by: Austin Horstman <khaneliman12@gmail.com>
Fix so that you can still generate `programs.helix.extraConfig` without
using `programs.helix.settings`. Useful particularly in the case of
`extraConfig = lib.readFile ./config.toml;`.
As I noticed in
<https://github.com/nix-community/home-manager/pull/7277#issuecomment-2985781610>,
it seems hyprland changed its domain name from `hyprland.org` to
`hypr.land`. (The old domain redirects to the new one)
These changes are made by the following:
find . \( -type d -name .git -prune \) -o -type f -print0 | xargs -0 sed -i 's/hyprland\.org/hypr.land/g'
Since we're creating a new derivation, we drop the original package
attributes. Add our own meta.mainProgram to resolve those warnings.
Signed-off-by: Austin Horstman <khaneliman12@gmail.com>
This is good for when displays are not considered part of the home configuration and are instead considered ephemeral.
Great for laptops but I use it for my desktop as well.
these hardcoded freeformat settings dont add anything over the default,
worse they generate empty sections which can then clash with user included config (my usecase).
It's best to move those to example.
so one can mix nix generated and manual configs
Instead of using `readFile` on the generated file, we included the generated config to avoid IFD. Because this approach makes ~/.config/meli/config.toml less readable (it referecens another generated file) I disabled it when the user does not "include" personal config. This feels a bit hackish but this is the best way I could find to keep the best of both worlds.
* Translate using Weblate (Basque)
Currently translated at 13.5% (5 of 37 strings)
Add translation using Weblate (Basque)
Co-authored-by: Muxutruk <benat.eigurenzu@elorrieta-errekamari.com>
Translate-URL: https://hosted.weblate.org/projects/home-manager/cli/eu/
Translation: Home Manager/Home Manager CLI
* Add translation using Weblate (Basque)
Co-authored-by: Languages add-on <noreply-addon-languages@weblate.org>
* Translate using Weblate (Basque)
Currently translated at 50.0% (8 of 16 strings)
Translate using Weblate (Basque)
Currently translated at 21.6% (8 of 37 strings)
Translate using Weblate (Basque)
Currently translated at 25.0% (4 of 16 strings)
Co-authored-by: Muxutruk <benat.eigurenzu@elorrieta-errekamari.com>
Translate-URL: https://hosted.weblate.org/projects/home-manager/cli/eu/
Translate-URL: https://hosted.weblate.org/projects/home-manager/modules/eu/
Translation: Home Manager/Home Manager CLI
Translation: Home Manager/Home Manager Modules
---------
Co-authored-by: Muxutruk <benat.eigurenzu@elorrieta-errekamari.com>
Co-authored-by: Languages add-on <noreply-addon-languages@weblate.org>
Fix an issue where the generated ~/.config/nvim/init.lua lacks a newline after the vim.cmd [[source ...]] directive. Without this newline, subsequent lua configuration is concatenated onto the same line, breaking lua syntax.
init.lua Before:
vim.cmd [[source /nix/store/...]]vim.opt.rtp:prepend(...)
After:
vim.cmd [[source /nix/store/...]]
vim.opt.rtp:prepend(...)
