Alfredo Di Napoli alfredo.dinap...@gmail.com writes:
Hello nixers,
I think I'm having a very similar problem here which I do not have enough
nix knowledge to debug. I have reinstalled nix-1.7 doing this (as suggested
from the nix website):
curl https://nixos.org/nix/install | sh
So
Now that that it does make sense to think about moving your .vim config
into nix space it also makes sense to package most commonly used
plugins. Thus if you think a plugin is missing in vimPlugins send me a
private mail and I'll try to include it using the vimp-pi = nix export
when creating the
On Sat, Oct 25, 2014 at 05:45:34PM +0200, Nicolas Pierron wrote:
We have 2 solution, either we stop the regressions when a pull request
(PR) is made, or we stop it when the fire is in. The fireman role is
hard to keep, and we should be verifying as much as possible at the PR
time. Also, if
Hello Nixers,
installing tmux-1.9a (latest) on a fresh Yosemite machine fails with:
gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../compat -I../include -I../include
-DTINYTEST_LOCAL -D_THREAD_SAFE -g -O2 -Wall -fno-strict-aliasing
-Wno-deprecated-declarations -D_THREAD_SAFE -c -o regress-tinytest.o
I wrote that on github, but will copy-paste here:
1) We have to remove the old code from vim/configurable.nix (I mean the
part of plugins loading
https://github.com/NixOS/nixpkgs/blob/15bb4c20e614ed6835c59c7c9101ee59eacbe473/pkgs/applications/editors/vim/configurable.nix#L7
)
2) Maybe it's a good
4) And I thin[*k*] we have to rename `dependencies` to smth like
`runtimeDependencies` and make them the same type as `buildInputs`, not the
Well runtimeDependencies could be executable tools. That dependencies
attr only lists vim plugin names. We could flag derivations to be a vim
plugin and
Alfredo Di Napoli alfredo.dinap...@gmail.com writes:
On the silver lining, nix-1.7 works out of the box on Yosemite :)
How is that possible? What are you doing to make it work? There's a major
effort underway right now by Joel Taylor and Dan Peebles to get a stdenv
working for Yosemite...
Hi John,
I swear, I did nothing!
Just installed Nix, xcode and all its additional CLI components, in this order!
Happy to help dissecting my machine to gather additional insights :)
Alfredo
Sent from my iPad
On 27/ott/2014, at 17:07, John Wiegley jo...@newartisans.com wrote:
Alfredo Di Napoli
On Sat, Oct 25, 2014 at 05:45:34PM +0200, Nicolas Pierron wrote:
We have 2 solution, either we stop the regressions when a pull request
(PR) is made, or we stop it when the fire is in. The fireman role is
hard to keep, and we should be verifying as much as possible at the PR
time. Also, if
I think the following steps could be done without too much damage:
- IRC bot that reports build failures for a range of commits once
nixos-combined jobset is done
- email to commiters that broke the the build (with a range of commits and
list of builds failed)
- nixos channel updates only when
- IRC bot that reports build failures for a range of commits once
nixos-combined jobset is done
Would be nice
- email to commiters that broke the the build (with a range of commits and
list of builds failed)
Would be nice
- nixos channel updates only when there are zero failures on jobset
Hi,
just want to link this discussion to a related issue:
https://github.com/NixOS/nix/issues/382
The symptoms seems to be that 10.9 + XCode 5.1 and 10.10 + XCode 6.1 work fine,
but 10.9 + XCode 6.1 shows the hickups described in this thread.
I am very new to nix, so I am not sure I can
Hi,
Does anyone know why the nixpkgs expression for ino pulls in minicom
instead of picocom? ino serial only looks for picocom.
Best regards,
Bjørn Forsman
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
13 matches
Mail list logo
