25 Aug 2024 |
Artur Manuel | check if its on nixpkgs (in your case, it is on nixpkgs), and then add it to extraEmacsPackages | 00:48:55 |
Artur Manuel | i think the codeblock already shows how you would regularly add a package | 00:49:33 |
Artur Manuel | * i think the codeblock (https://github.com/nix-community/emacs-overlay?tab=readme-ov-file#emacs-from-git-and-latest-including-pre-releases) already shows how you would regularly add a package | 00:51:52 |
Artur Manuel | * i think the codeblock [https://github.com/nix-community/emacs-overlay?tab=readme-ov-file#emacs-from-git-and-latest-including-pre-releases] already shows how you would regularly add a package | 00:52:47 |
Artur Manuel | wrapProgram caused whatever tried to compile first to fail | 01:41:24 |
Artur Manuel | i genuinely do not know how i could wrap texlive with emacs lol im stumped | 01:42:24 |
Artur Manuel | * i genuinely do not know any other ways i could wrap texlive with emacs lol im stumped | 01:42:33 |
Artur Manuel | yeah my idea coffers are completely barren | 02:08:40 |
Artur Manuel | rest in peace purity, im throwing in the towel | 02:15:19 |
26 Aug 2024 |
adisbladis | Tbh I don't think that we should patch the emacs sources to point to every executable that it supports invoking in every mode | 02:56:14 |
adisbladis | It's OK to expect a user to pull in some packages into the environment | 02:56:29 |
adisbladis | Emacs is already huge, and I don't want to blow up our closure even more | 02:56:46 |
adisbladis | Native-comp made it grow by a few times.. | 02:57:03 |
adisbladis | But that's functionality that all users benefit from | 02:57:27 |
Artur Manuel | yea thats fair, i was more aiming towards patching it myself because i needed to be able to export .pdf files | 03:06:03 |
Artur Manuel | And my main issue was i just didnt have the ability to do that | 03:06:34 |
adisbladis | I'll usually add a tex environment to a nix-shell since I always end up customising extensions anyway | 03:07:22 |
Artur Manuel | * And my main issue was i just didnt have the ability to do that (without installing it directly into my system and needing a "surprise dependency") or attempting to embed the tex suite into emacs to make sure that i dont have get surprised by it not working because no texlive | 03:08:00 |
adisbladis | And I don't necessarily want an everything-and-the-kitchen-sink texlive globally | 03:08:06 |
Artur Manuel | In reply to @adis:blad.is I'll usually add a tex environment to a nix-shell since I always end up customising extensions anyway I'd do this but then it would make moving around systems need my own nix shell everytime i need emacss tex support or whatever have you | 03:09:22 |
Artur Manuel | while trying to automate a 5 minute task in 2 days isnt really productive, it saves time once 2 weeks go by | 03:11:14 |
adisbladis | I may also not see the point in wrapping Emacs since I launch everything from within Emacs :P So wrapping Emacs is equivalent to environment.systemPackages for me. | 03:12:00 |
Artur Manuel | More so i can just nix run on any system i please | 03:12:25 |
adisbladis | In reply to @asmundesen:matrix.org More so i can just nix run on any system i please Maybe just another layer of wrapper then? | 03:12:57 |
Artur Manuel | Mac (id have to make use of emacs plus in times like this) a non nixos system, wtc | 03:13:04 |
adisbladis | Wrap Emacs to setup PATH | 03:13:05 |
adisbladis | Either that, or use home-manager | 03:13:27 |
Artur Manuel | yknow thats actually a solid idea, i could just make an emacs package and setup another wrapper | 03:16:20 |
27 Aug 2024 |
| @poorguy:pleasemakemeri.ch left the room. | 02:08:51 |
28 Aug 2024 |
| abbé changed their display name from abbe to abbé. | 03:28:45 |