Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

My emacsGcc overlay is not working #146

Closed
codygman opened this issue Mar 1, 2021 · 2 comments
Closed

My emacsGcc overlay is not working #146

codygman opened this issue Mar 1, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@codygman
Copy link
Contributor

codygman commented Mar 1, 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:

  • overlays
  • overrides
  • extern
@codygman codygman added the bug Something isn't working label Mar 1, 2021
@ursi
Copy link

ursi commented Mar 1, 2021

It would help if debugging flakes were easier

You can use builtins.getFlake to get a hold of your flake in a repl, that can be useful for debugging.

@nrdxp
Copy link
Collaborator

nrdxp commented Mar 2, 2021

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
@nrdxp nrdxp closed this as completed in 7c226c9 Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants