bug: Alacritty doesn't show up in Applications (OSX)

[jjant]

Are you following the right branch?

• [X] My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

• [X] I have searched the existing issues

Issue description

I tried to install alacritty with home manager in OSX Monterey and it doesn't show up in my Applications, so I can't easily launch it standalone (I can only run alacritty from an existing terminal).

This is my ~/.config/nixpkgs/home.nix:

{ configs, pkgs, ... }:
{
  home.username = "something";
  home.homeDirectory = "/Users/something";

  home.stateVersion = "22.05";

  home.packages = [
    pkgs.neovim
  ];

  programs.home-manager.enable = true;

  programs.alacritty = {
    enable = true;
    settings = {
      font.size = 15;
    };
  };
}

Maintainer CC

Maybe @hyperfekt @rycee?

System information

 - system: `"aarch64-darwin"`
 - host os: `Darwin 21.6.0, macOS 12.5.1`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.11.0`
 - channels(jjantdev): `"home-manager-22.05.tar.gz"`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

[loicreynier]

In my experience Alacritty closing immediately is caused by missing drivers. In that case this is an issue related to your system rather than a Home-Manager issue. On my system I use nixGL to wrap Alacritty and fix the driver issue.

[jjant]

@loicreynier Thanks, it turns out that that was a separate issue (a program was crashing on startup, I could debug it with alacritty --hold). I've updated the issue to only mention the current problem (alacritty not showing up in applications).

[loicreynier]

I have no experience in Nix on macOs but from the Nix package source it seems that "Applications" files are copied to the environment. If I understand correctly, I don't think it is related specifically to Alacrity. Do you have any other Home-Manager programs installed that are appearing in "Applications"? If not you may have a look at issue #1341.

[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.

[utkarshgupta137]

Not stale

[ncfavier]

Is there any reason to believe that this isn't a duplicate of https://github.com/nix-community/home-manager/issues/1341?

[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.