<supersandro2000>
Mic92: Could it be that the nix-shell in nixpkgs-review with multiple PRs is not changing the directory correctly?
<Mic92>
supersandro2000: could be
<Mic92>
I am not using this option that often
<supersandro2000>
the build.nix are in the correct directory according to the logs but you never change it when quitting the first one
<supersandro2000>
I would actually need that feature to get a clean logs directory
<supersandro2000>
otherwise my custom shell prompt always checks all packages of the log files instead of the current PR ones
cmacrae has joined #nix-darwin
<cmacrae>
Hey people o/ I've been trying to keep an eye on Big Sur related issues in nixpkgs. Are people here using Nix on Big Sur? Most things working?
<cmacrae>
Also curious to hear if anyone ran into issues with Nix when upgrading form Catalina?
<aterius>
I'm using it
<aterius>
I haven't had any issues
<aterius>
Some things were broken with the changes to mac stdenv, like libhandy
<aterius>
but otherwise seems fine
<cransom>
if you rely on nixpkgs not from a few weeks ago, you'll have issues building under big sur
<antifuchs>
cmacrae: I've seen some linking issues and some other issues where older versions of the overall system SDK are pulled in that don't understand newer options
<cmacrae>
Thanks for chiming in here, all!
<cmacrae>
Really apperciate it
<aterius>
antifuchs: Yeah the linking issues was what I was referring to
<cmacrae>
Any issues with upgrading? I remember going to Catalina and how much of an issue that was
<cransom>
i usually update, but some work repos need some updates yet and i have to shepherd some users, so i'm going to feel more comfortable around a .1 release likely.
<aterius>
I haven't had any problems except with imessage crashing intermittently
<aterius>
my MBP is also getting fairly old though
<cmacrae>
I think I'll give Big Sur a shot on my personal MBP then :)
<aterius>
There's also not any killer features if you're not running an M1 mac (which would come with it anyways)
<cmacrae>
I've heard, generally, that it's been more stable for people
<{^_^}>
#103933 (by nuance, 2 weeks ago, open): emacs: Link native-lisp directory into Mac app
<aterius>
antifuchs this solves the issue with opening emacs.app
<antifuchs>
omg
<antifuchs>
that sounds awesome
<antifuchs>
I think there's an upstream issue in the emacs BTS about this too; I thought to fix this with some code changes to add path lookups, but this is much better
<antifuchs>
chimed in & submitted my approval of the pr (:
<aterius>
Yeah I saw that, I figured it doesn't hurt to merge this while we wait...
<aterius>
I've been patching this in my fork of emacs-overlay
<aterius>
*for awhile
<aterius>
Oh another big sur issue is I've noticed more flickering of emacs, not measured or anything
<aterius>
Wait I didn't realize Andrea closed the issue
<antifuchs>
yeah, I think I reported two kinds of root causes, and Andrea fixed one