brave -> zen, and more apps ride matugen #103
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "tweaks"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
zenreplacesbraveas the browser onishtar- DNS-level adblock carries the network side now, so brave's built-in blocker stopped earning its keep and theming was the drawzen-browserinput (0xc000022070/zen-browser-flake, followsnixpkgs+home-manager) - not in nixpkgs, firefox-fork on its own cadencehomeModules.beta): telemetry-offpolicies+policies.ExtensionSettingsforce-installing uBlock Origin / Bitwarden / Stylus from AMO (keyed by webext id)profiles.*declared, on purpose - the HM firefox module writesuser.js/chromeas read-only symlinks, which would clobber noctalia'szen-browsertemplate (it injects userChrome/userContent css into the live profile + flips the legacy-stylesheets pref). leaving the profile unmanaged keeps it writable so noctalia owns the theme - same split asbat/btopdotfiles/niri/config.kdl:Mod+B+ the PiP float rule move tozen-beta(wrapFirefox names the beta variant's binary + app-idzen-beta, notzen)nvimfollows noctalia's matugen palette now -ishtar-only, on top of the standalone nvf scope from #101base16-nvim+ a bootstrap thatdofiles the palette noctalia renders to~/.config/nvim/lua/matugen.lua(its "neovim" template); noctalia owns only that one mutable filebase16-nvimdoesn't fireColorScheme(so transparency reapply is manual), andNVIM_APPNAME=nvfbreaks noctalia's own generated handler (require('matugen')falls offpackage.path), so we stubnew_signalacross thedofileand register one reload ourselvesbtoppointed at noctalia's generated theme (color_theme = "noctalia")btop.confis an HM read-only symlink, so noctalia'sapply.shcan't sed it in - setting the pointer in nix means apply.sh no-ops instead.batneeded the opposite (nothing): its config isn't HM-owned, so noctalia's template writes--theme+ builds the cache itselfxdg-desktop-portal-gnome+ aportals.confnaminggtkas theFileChooserfallback, but never pulls the gtk backend in, and gnome's impl doesn't render outside a gnome session -> no workingFileChooserprofiles/niri.nix: addxdg-desktop-portal-gtk+ pinFileChooser = "gtk"(theconfig.nirioverride wins for that one interface, rest of niri-flake's portal config stays). needs a relog - portal services are session-scopedfirefoxstaysenabled inlamentDesktopas a backup until zen's proven; brave flatpak + its niri leftovers come out after cutovernativeMessagingHostsonly if the desktop handshake's wantedlatest.xpiat profile-init (auto-updating, not closure-pinned); NURfirefox-addonsis the pin-it route if ever wanted