| 8 Sep 2023 |
|  @ulli:hrnz.li left the room. | 20:41:32 |
| 9 Sep 2023 |
 woobilicious | Is that doom upstream, or the nix package? | 02:26:45 |
 mei š& | woobilicious: JoelMcCracken's last messages were about doom itself | 03:11:27 |
| woobilicious | Ahh okay :-) | 03:12:13 |
| woobilicious | I wouldn't mind moving to a "simple-emacs" thing using nix that lets me quickly setup a decent setup of emacs without having to learn lisp. | 04:05:00 |
| mei š& | i've changed my mind a bit on that since then | 04:06:42 |
| mei š& | i think doom having its own module system is good, but it should be way more modularized. almost like nixpkgs' evalModules is reusable. it shouldnt be a part of The Big Doom Blob | 04:07:19 |
| mei š& | but evaling files conditionally gets like, the vast vast majority of the way there. and we can get rid of doom sync with the stuff we talked about before | 04:08:48 |
| mei š& | tl;dr emacs has survived for a very long time and we should learn from its design and try to mimick it | 04:09:37 |
| woobilicious | I moved to doom emacs because spaceemacs was always broken for me lol. | 04:15:51 |
|  jakra joined the room. | 08:37:16 |
| jakra | Can someone help me? I've got doom-emacs installed via home-manager on nixos, with the config directory set as ./doom.d. In that folder (relatively to home manager config) I've got init.el, packages.el, custom.el and config.el.
My config.el changes are reflected in doom after a switch (I can see them when I "find file in private config", but my changes to init.el aren't there.
Is this expected? | 08:41:59 |
| jakra | Or, more likely, I'm being an idiot, and loading the wrong flake! š° | 08:58:01 |
 Peter Tonner | I'm trying to get an initial setup working, is it normal for emacs to be running a bunch of async native compilation in the background? During build there was already a bunch of native comp done, so I'm not sure why this also happening. I've been letting it run in the background for a while but there doesn't seem to be an end in sight. This is my setup:
{ inputs, pkgs, ... }:
{
imports = [ inputs.nix-doom-emacs.hmModule ];
programs.doom-emacs = {
enable = true;
doomPrivateDir = ./doom.d;
};
}
| 13:10:23 |
| Peter Tonner | I've also tried the solution added by this feature, but it didn't seem to make a difference: https://github.com/nix-community/nix-doom-emacs/pull/303 | 13:15:03 |
| Peter Tonner | oh, maybe this is just a new-er design of doom? https://github.com/doomemacs/doomemacs/commit/3853dff5e11655e858d0bfae64b70cb12ef685ac | 13:19:43 |
| Peter Tonner | I had stepped away from doom for a while but am trying it again, so hadn't seen this change before | 13:20:11 |
| Peter Tonner | is there any way to enable the --aot flag on the nix side? I feel like i'd prefer to just compile everything before running, even if it's going to take forever | 13:23:55 |
| 10 Sep 2023 |
|  @rickbonavigo:matrix.org left the room. | 08:28:51 |
| 11 Sep 2023 |
 JoelMcCracken | I think Iām going to go back to installing doom outside of nix for a little while, how hlissner does it | 00:37:56 |
| woobilicious | Am I the only one who looses lsp functions when opening a file with root? SPC f U, this didn't happen with doom outside of nix, I installed nil globally, and with extraPackages in home manager, but it still throws an error. | 02:38:47 |
| mei š& | woobilicious: i think you have to do some extra things when you're using the remote thing with the name I don't remember | 12:44:01 |
| mei š& | * woobilicious: i think you have to do some extra lsp configuration when you're using the remote thing with the name I don't remember | 12:44:14 |
| woobilicious | I swear it use to work till I migrated to the nix repo oh well š¤·āāļø | 21:27:21 |
| 12 Sep 2023 |
|  @chrispickard:matrix.org removed their display name chrispickard. | 17:38:28 |
| JoelMcCracken |
remote thing
tramp?
| 18:23:11 |
| JoelMcCracken | *
remote thing
tramp?
| 18:23:16 |
| 14 Sep 2023 |
 @asbjorn:olli.ng | Sooo...
I'm running into this issue: https://github.com/nix-community/nix-doom-emacs/issues/381
Basically my SPC / isn't working because of issues upstream.
But as the comment on #381 says, it seems to already be fixed upstream.
However, the link to doomemacs upstream in flake.nix hasn't been updated since this commit
I tried forking the nix-doom-emacs repo, and updating the ref manually- but nix build fails with some error messgaes that are pretty opaque to me.
Have any of you guys looked at this too?
Has anyone successfully overridden the upstream emacs input?
...or any other approach to getting SPC / working again? | 15:24:16 |
| @asbjorn:olli.ng | * Sooo...
I'm running into this issue: https://github.com/nix-community/nix-doom-emacs/issues/381
Basically my SPC / isn't working because of issues upstream.
But as the comment on #381 says, it seems to already be fixed upstream.
However, the link to doomemacs upstream in flake.nix hasn't been updated since this commit
I tried forking the nix-doom-emacs repo, and updating the ref manually- but nix build fails with some error messgaes that are pretty opaque to me. Seems like it has something to do with the .patch files.
Have any of you guys looked at this too?
Has anyone successfully overridden the upstream emacs input?
...or any other approach to getting SPC / working again? | 15:35:10 |
| @asbjorn:olli.ng | * Sooo...
I'm running into this issue: https://github.com/nix-community/nix-doom-emacs/issues/381
Basically my SPC / isn't working because of issues upstream.
But as the comment on #381 says, it seems to already be fixed upstream.
However, the link to doomemacs upstream in flake.nix hasn't been updated since this commit
I tried forking the nix-doom-emacs repo, and updating the ref manually- but nix build fails with some error messgaes that are pretty opaque to me.
(Seems like it has something to do with the .patch files.)
Have any of you guys looked at this too?
Has anyone successfully overridden the upstream emacs input?
...or any other approach to getting SPC / working again? | 15:38:25 |
