| 7 Sep 2023 |
 ckie (they/them) | i'm thinking i might end up giving up doom because it seems to be kinda stalled. but the straight stuff is great regardless | 15:06:18 |
| ckie (they/them) | * i'm thinking i might end up giving up doom eventually because it seems to be kinda stalled. but the straight stuff is great regardless | 15:07:37 |
|  woobilicious joined the room. | 17:11:46 |
| 8 Sep 2023 |
 JoelMcCracken | yeah its hard to say | 03:10:42 |
| JoelMcCracken | doom is tricky | 03:10:49 |
| JoelMcCracken | it just has soo much code | 03:11:03 |
| JoelMcCracken | its quite a big project, too big imo | 03:11:08 |
| JoelMcCracken | not to say that like there aren't good reasons for all that code; i d; | 03:11:34 |
| JoelMcCracken | (that I can't comment) | 03:11:44 |
| JoelMcCracken | but i can say that most of it just really doesnt seem very simple | 03:11:55 |
| JoelMcCracken | ive been wondering if thats why it has stalled | 03:12:14 |
| JoelMcCracken | * ive been wondering if thats why it has stalled; the big refactor is ending up in a big mess | 03:12:40 |
| JoelMcCracken | but, FYI, I think doom development is now un-stalling | 04:01:49 |
|  hrnz left the room. | 20:41:32 |
| 9 Sep 2023 |
| woobilicious | Is that doom upstream, or the nix package? | 02:26:45 |
| ckie (they/them) | 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 |
| ckie (they/them) | i've changed my mind a bit on that since then | 04:06:42 |
| ckie (they/them) | 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 |
| ckie (they/them) | 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 |
| ckie (they/them) | 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 |
