01:01 <multun> I finaly got it

01:02 <multun> it was an aweful sum of bugs, most of which only got workarounds

01:03 <multun> the best of all being...

01:03 <multun> the build failing because the version contains a dot

01:03 <multun> for some unknown emacs lisp reason

13:28 <multun> this is madness

13:28 <multun> some version number cause the build to fail, some others don't

13:28 <multun> http://paste.awesom.eu/smXq&ln

13:34 <multun> oh my fucking god, the build fails when the version is 13 characters long

13:34 <multun> what an awesome easter eegg

20:10 <iqubic> I'm sure there are a few people in here who have run into this issue apart from me. Many Emacs packages built to facilitate programming, like company's auto completion, or flycheck's underlining of errors only work if Emacs can find the libraries that I'm using. One way of doing this is to launch Emacs from inside a nix-shell. However, as a user of EXWM, it seems really quite silly to launch a second instance of Emacs.

20:11 <iqubic> Is there a prefered method for getting EXWM to "see" the libraries and packages I'm pulling in from my nix-shell, without needing to start a second Emacs instance?

21:17 <multun> you can use compile commands databases if relevant

21:18 <multun> that's what I use for C/C++ projets

21:18 <multun> projects

21:18 <iqubic> How would that help.

21:18 <multun> It helps emacs discover the path to headers

21:18 <multun> just feed it into irony

21:20 <iqubic> but what if you were to install some C/C++ libraries using Nix-Shell? How would you get emacs to discover the path to those?

21:21 <multun> well emacs doesn't have to, because everything is in the compilation database

21:22 <multun> I use bear to generate it in the first place