Re: [Nix-dev] How to configure neovim?
I'm still having no solution here, so I'm sorry to reach out again. I could send you my complete vim/neovim setup, if you want (6 nix files, several .vim files). On 18-10-2015 22:02:10, Matthias Beyer wrote: > On 18-10-2015 19:20:51, Rok Garbas wrote: > > your snippets look ok. there must be something you're missing. > > > > does you system nvim point to /nix/store/...-neovim-2015-06-09-configured? > > It does not, it points to: > > /nix/store/9g54k2nk9ar4rywr0b8c7r3dg1qv6718-neovim-2015-06-09/bin/nvim > > I do not have nvim in my user environment installed, so this must be > the system wide install. > > I don't know where else to look... > > -- > Mit freundlichen Grüßen, > Kind regards, > Matthias Beyer > > Proudly sent with mutt. > Happily signed with gnupg. -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg. signature.asc Description: PGP signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Ideas for a NixOS-related bachelors thesis?
On 02-11-2015 09:06:17, Vladimír Čunát wrote: > > Source mirroring is a thing completely independent of nix(os), so it > might have much larger chance of being successful, as P2P IMHO pays off > only when you get many clients. > This sounds rather interesting to me, though I'm not sure whether this is actually a challenge. The one thing one'd need to do is to build a tool which does (for example) {github,sf,foobar} -> IPFS, which is kind of a bash script. And yes, I also see that this is completely independent of nixos. Building a nix backend, so we can have `buildFromIPFS {...}`, would be more challenging, I guess. -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg. signature.asc Description: PGP signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] NixCon: Last week to get your NixCon ticket
Hi everybody, Preparations for NixCon are in full swing. Here is a quick update from last time: !!! IMPORTANT !!! - On Monday, 9.11.2015, we will close ticket sale. This still gives you 7 days to get your ticket in case you are waiting for the last week. (we need to close ticket sales 4 days prior to conference to be able to report accurate number for catering) http://conf.nixos.org/#sprinting - At the time of writing we issued 75 tickets. - After conference sprint (Monday/Tuesday) will happen at RhodeCode GmbH office (Wallstrasse 27, 10179 Berlin) http://conf.nixos.org/#sprinting - Talks are going to be recorded. Yaay! All the "thank you" should go to "CCC Video Operation Center" (http://c3voc.de). Looks like they are also looking into NixOS for their special needs. If somebody wants to give them a help with NixOS evaluation, then after conference sprint is going the be the perfect time - Basically we (organizers) are extremely excited and can not wait for conference to start. It is going to be amazing! If you think we forgot something or we did not provide enough information let us know via Twitter (@NixConBerlin) or via Email (c...@nixos.org). We are only humans, for now :). See you (very soon) in Berlin! -- NixCon 2015 organizers signature.asc Description: signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Ideas for a NixOS-related bachelors thesis?
On 11/01/2015 10:16 PM, Ericson, John wrote: > If I recall Eelco's thesis correctly, the derivation is built in a > temporary location, the build is hashed, and then the binary is mangled > so the temp path is replaced with the proper /path/to/store/hash/ path. > Well if we just stick the data in IPFS before the path replacement, and > let the other side do the mangling we dodge that problem. I don't think that would work, as hash rewriting *changes* the standard hash of the path (self-referencing problem). Nitpicks: you all seem to use "intentional" instead of "intensional", but the name doesn't really matter, which is incidentally the only thing that would much change during ex->in switch. I don't really get why people call for it so much. The only useful (possible) consequence I can think of is that when we e.g. update some build tool, the builds using this tool would likely result into the same path, so the rebuild would *not* cascade like it does now. It would only cut non-runtime indirect dependencies, which isn't really so much, and we would have to deal somehow with the equivalence classes allowing such "sharing". Source mirroring is a thing completely independent of nix(os), so it might have much larger chance of being successful, as P2P IMHO pays off only when you get many clients. Vladimir smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] How to stop all packages to stop compiling from binary
When using a channel you should have the core packages available as binaries. What is your cache configuration in nix.conf? Do you have any overrides? Dnia 1 listopada 2015 22:22:34 CET, rohit yadavnapisał(a): >Hi All- > >I upgraded my channel from 14.12 to 15.09 and now all the packages are >being compiled from source. How do I make it to get the pre-build >binaries? > >Thanks, >Rohit > > > > >___ >nix-dev mailing list >nix-dev@lists.science.uu.nl >http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Wysłane za pomocą K-9 Mail.___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev