You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would help if debugging flakes were easier with the repl here. I'm also not sure how to use nix run to test just emacsGcc, so that makes this harder to debug.
Maybe the root cause of my misunderstanding here can help improve documentation. On that note it might be useful to mention that extern is the easiest place to add things like emacsOverlay or sops-nix.
Because honestly I went in this order kind of guessing where to add emacs-ovetlay:
overlays
overrides
extern
The text was updated successfully, but these errors were encountered:
We should probably switch the order of these overlays. It looks like emacsGcc comes from emacs-overlay, but external overlays are applied after devos's overlays.
Can you try this locally and see if it resolves the issue? I believe it will. Wondering if we should put extern.overlays at the very top, before even packages, or if putting just above the overlays dir is sufficient.
codygman
added a commit
to codygman/devos
that referenced
this issue
Mar 2, 2021
My emacsGcc overlay isn't taking affect? Or perhaps how I could debug why?
Overlay: https://github.com/codygman/devos/blob/gccemacs/overlays/emacsGcc.nix
Place I install emacsGcc and expect that overlay to add those packages:
https://github.com/codygman/devos/blob/a3339192369aafe82bd4b053249ef2d418b69fe0/profiles/develop/emacs/default.nix#L4
It would help if debugging flakes were easier with the repl here. I'm also not sure how to use
nix run
to test just emacsGcc, so that makes this harder to debug.Maybe the root cause of my misunderstanding here can help improve documentation. On that note it might be useful to mention that extern is the easiest place to add things like emacsOverlay or sops-nix.
Because honestly I went in this order kind of guessing where to add emacs-ovetlay:
The text was updated successfully, but these errors were encountered: