| 3 Feb 2023 |
JoelMcCracken | how do you actually run the emacs built with nix-doom-emacs? just use e.g. emacs in ~/.nix-profile? | 02:47:48 |
mei π& | sure if you've configured it like that (you probably did if you're using the HM module) | 14:43:59 |
mei π& | ~/.nix-profile/bin should be in PATH | 14:44:15 |
mei π& | you can also use services.emacs | 14:44:22 |
JoelMcCracken | =) thank you | 17:08:10 |
| 4 Feb 2023 |
JoelMcCracken | so right now i'm running https://github.com/joelmccracken/workstation/pull/10, building it on my local computer with nix build --verbose --no-link ~/workstation/#homeConfigurations.${WORKSTATION_NAME}.joel.activationPackage --show-trace --print-out-paths --rebuild, and activating with "$(nix path-info ~/workstation/#homeConfigurations.${WORKSTATION_NAME}.joel.activationPackage)"/activate. | 01:51:14 |
JoelMcCracken | when I boot emacs, its (roughly) totally broken however | 01:51:45 |
JoelMcCracken | this is on macos | 01:52:06 |
JoelMcCracken | the Warnings buffer says:
Warning (initialization): An error occurred while loading β/nix/store/4zw8l9f2ybgq5klckdl5dh9ygvcghq32-emacs-28.2/lib/emacs/28.2/native-lisp/28.2-78b7c535/warnings-28e75f4d-870b026e.elnβ:
Doom hasn't been initialized yet; did you remember to run 'doom sync' in the shell?: /nix/store/9prmp4wm3y282kdjbmdmksmija0p38m6-straight-emacs-env/etc/@/init.28.elc
To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file. Start Emacs with
the β--debug-initβ option to view a complete error backtrace. Disable showing Disable logging
| 01:53:03 |
JoelMcCracken | any thoughts or advice would be very appreciated | 01:53:14 |
JoelMcCracken | also, does anyone happen to have an example of nix-doom-emacs which is using the standalone home manager setup as a flake on macos? | 03:06:01 |
JoelMcCracken | ugh, i believe I've figured out my problem | 03:53:43 |
JoelMcCracken | nvm | 03:53:49 |
JoelMcCracken | for anyone who happened to come across my message here or elsewhere, the issue was that I had content from an already extant doom-emacs install in ~/.emacs.d, and that seemed to be interfering with the way nix-doom-emacs is configured; | 19:44:08 |
JoelMcCracken | hmm, I rely fairly heavily on SPC *, seems broken | 22:06:57 |
| 5 Feb 2023 |
alicecandyOM | In reply to @alicecandyom:krendelhoff.space
here is workaround I did to fix it:
(use-package! consult
:config
(defun consult--ripgrep-builder (&rest args) (apply (consult--ripgrep-make-builder) args)))
fix | 11:33:53 |
JoelMcCracken | Been tracking various things down, I almost wonder if I should add some of these notes to the readme or something? the ripgrep/ SPC * problem seemed to be because nix-doom-emacs doesn't import any environment variables (and hence path) into the emacs exec path; fixing that fixed one of the problems I saw. There is till an issue with the vertical completion package trying to execute a funciton that doesn't exist, i'm wondering if there is a version mismatch somehow | 19:41:28 |
| 6 Feb 2023 |
akaihola | Ha! Adding po-mode from MELPA was as simple as
{ config, pkgs, ... }:
let
doom-emacs = pkgs.callPackage (builtins.fetchTarball {
url = https://github.com/nix-community/nix-doom-emacs/archive/master.tar.gz;
}) {
doomPrivateDir = ./doom.d;
emacsPackagesOverlay = self: super: {
po-mode = pkgs.emacsPackages.po-mode;
};
};
in {
home.packages = with pkgs; [
doom-emacs
];
}
| 20:23:09 |
akaihola | * Ha! Adding po-mode from MELPA was as simple as
{ config, pkgs, ... }:
let
doom-emacs = pkgs.callPackage (builtins.fetchTarball {
url = https://github.com/nix-community/nix-doom-emacs/archive/master.tar.gz;
}) {
doomPrivateDir = ./doom.d;
emacsPackagesOverlay = self: super: {
po-mode = pkgs.emacsPackages.po-mode;
};
};
in {
home.packages = with pkgs; [
doom-emacs
];
}
...but alas, it doesn't work. I get Invalid function: po-with-temp-buffer when opening a .po file.
| 20:24:32 |
| 7 Feb 2023 |
| Faez Shakil joined the room. | 09:20:13 |
majorgreys | Starting from scratch here with nixos and wondering if I should be using home-manager? my main use for this nixos system is for development and really just need it to have my doom.d. | 18:32:59 |
JoelMcCracken | do you hvae much prior experience with nix ? | 23:06:01 |
| 10 Feb 2023 |
| hexagony joined the room. | 02:05:48 |
| 12 Feb 2023 |
| TheSirC joined the room. | 13:47:08 |
| 15 Feb 2023 |
mei π& | hey k0kada (he/him) i have had this annoying bug for a while i wonder if you also do | 12:59:20 |
mei π& | in mu4e-compose-mode, (evil-backward-char) which is the backspace key takes like ~500ms and freezes the emacs render when the message is over a few kb's | 12:59:53 |
mei π& | seems to scale with buffer size and I'm not sure if it's worth telling upstream | 13:00:25 |
mei π& | * seems to scale with buffer size and I'm not sure if it's worth telling upstream since we 'r weird | 13:00:33 |
k0kada (he/him) | Not this one | 13:01:46 |
k0kada (he/him) | But NDE is becoming more and more broken with each emacs-overlay upgrade, that is for sure | 13:02:05 |