In reply to @sg-qwt:nltrix.net

hi folks, I've got a pretty basic fresh setup from master nix-doom-emacs and master emacs-overlay like below, nothing fancy

programs.doom-emacs =  {
        enable = true;
        doomPrivateDir = ../config/doom-emacs;
        emacsPackage = pkgs.emacsPgtkNativeComp; 
     }

on fresh doom emacs start, I've got Error (doom-init-ui-hook): Error running hook "+doom-dashboard-init-h" because: (void-function doom-modeline-set-project-modeline) , I also noticed magit status does not startup due to similar error function is void: doom-modeline-set-vcs-modeline

does anyone encounter same issue here or know how to fix this?

In reply to @hab25:matrix.org
I encountered both issues. My workaround was to disable the dashboard and modeline doom modules in init.el.

haha..that's what i currently done..

on a deep thought though, there's logic error for my current flake dependency layout:

    emacs = {
      url = "github:nix-community/emacs-overlay";
      inputs.nixpkgs.follows = "nixpkgs";
    };
    
    nix-doom-emacs = {
      url = "github:nix-community/nix-doom-emacs";
      inputs.nixpkgs.follows = "nixpkgs";
      inputs.emacs-overlay.follows = "emacs";
    };

ideally, emacs would follow nix-doom-emacs.inputs.emacs-overlay, not the other way around, not sure if that's causing the problem though..

I'm not using emacs-overlay at all; I don't think it's related to that.

PS: Though it seems that most flakes-supporting projects recommend it, I think using follows is a bad idea, unless you are willing to sacrifice stability for faster builds. The reason is, when you do this you are overriding the pins that the developers tested with. Big disclaimer: I'm new to flakes.

in order to pin emacs-overlay exactly same as nix-doom-emacs, I ended-up with a single nix-doom-emacs flake input and used overlay like below

    nix-doom-emacs = {
      url = "github:nix-community/nix-doom-emacs";
      inputs.nixpkgs.follows = "nixpkgs";
    };
     overlays = [
          (import nix-doom-emacs.inputs.emacs-overlay.outPath)
     ];

but problem still exists, so I guess as hab25 said, that's something else then..

in order to pin emacs-overlay exactly same as nix-doom-emacs's input, I ended-up with a single nix-doom-emacs flake input and used overlay like below

    nix-doom-emacs = {
      url = "github:nix-community/nix-doom-emacs";
      inputs.nixpkgs.follows = "nixpkgs";
    };
     overlays = [
          (import nix-doom-emacs.inputs.emacs-overlay.outPath)
     ];

but problem still exists, so I guess as hab25 said, that's something else then..

In reply to @hexagonk:halogen.city
I've updated the issue I mentioned above; located an old working `doomemacs` commit.

In reply to @ckie:ckie.dev
hexagonk: the blocker is this PR failing. the overall flow is config -> doom init -> collect package names -> stick them all in one drv (+elc) -> bundle user config + packages + emacs into a drv

In reply to @ckie:ckie.dev
#308 running through my nixos pipeline now to test..

In reply to @k0kada:matrix.org
One thing that I saw is that doom-dashboard is broken, but it was already broken in the current pin in master