Do not overwrite .config/mimeapps.list to keep compatibility with GUI edits

[tobiasBora]

Description

I'd like to do something as simple as

  xdg.mimeApps = {
    enable = true;
    associations.added = {
      "x-scheme-handler/thunderlink" = [ "thunderbird-tl.desktop" ];
    };
  };

Unfortunately home manager complains about the fact that this file exists and is not managed by HM. Of course it is the case as KDE modifies that file regularly (for instance I guess when I change from Dolphin the default application to open a file). I would love to be able to keep this file managed by the OS and still use HM to configure parts of it.

Would it be possible to define a coexisting mode (e.g. xdg.mimeApps.coexistWithOs) in which xdg does not replace this file but would instead edit it using the xdg-mime tool? This was proposed before here for instance.

[x10an14]

This works for me

{config, pkgs, ...}:
let
  start-waybar = pkgs.writeShellApplication {
    name = "start-waybar.sh";
    runtimeInputs = with pkgs; [
      coreutils
      findutils
      gnugrep
      procps
      waybar
    ];
    text = ''
      function kill_previous_invocations() {
          # Kill earlier invocations of self
          pgrep "$(basename "$0")" |
              grep -v "$1" |
              xargs kill -9 2>/dev/null
      }

      set +e
      # Restart - make idempotent
      kill_previous_invocations $$
      pgrep -f 'waybar$' | xargs kill -s 15 2>/dev/null
      set -e

      # Start anew
      waybar
    '';
  };
in {
  home.packages = [start-waybar];
  programs.waybar = {
    enable = true;
    # more
  };

  wayland.windowManager.sway.config.startup = [
    {command = "exec ${start-waybar}/bin/start-waybar.sh"; always = true;}
  ];
}

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.