Haskell and Nix are completely different languages. Just because
they're both functional does not mean that they have a similar syntax.
Of course, syntax highlighting for Nix is still possible, and it would
be nice if we could make that available for more editors.
Andres
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
germsteel wrote:
> I have tried grubDevice "/dev/sda" and "/dev/sda1" all I get is the same
> unable to boot hd (0,0)
> i can always boot into the install/rescue iso and the install always fails
> with this message:
> 100 418K
> 2267 store paths in ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony White wrote:
> Or do the .nix files have a syntax of which is slightly different to haskell?
> If yes it's haskell syntax, I like syntax highlighting in editors. I
> use it a lot with css, php, javascript and xhtml, etc in kwrite.
> It makes spott
Hello,
According to :
http://nixos.org/about.html
"Nix is a purely functional package manager. This means that it treats
packages like values in purely functional programming languages such
as Haskell — they are built by functions that don’t have side-effects,
and they never change after they ha
2009/6/9 germsteel :
>
> Discovered on nixos, had to check it out.
>
> Trying to install nixos-0.1pre15831-i686-linux on VirtualBox Mac OS X
>
> I have followed the manual and have:
> created ext3 filesystem on /dev/sda1 and swap on /dev/sda2
> edited configuration.nix
> run nixos-install
>
> I hav
Discovered on nixos, had to check it out.
Trying to install nixos-0.1pre15831-i686-linux on VirtualBox Mac OS X
I have followed the manual and have:
created ext3 filesystem on /dev/sda1 and swap on /dev/sda2
edited configuration.nix
run nixos-install
I have tried grubDevice "/dev/sda" and "/dev
Hi,
Ludovic Courts wrote:
> Author: ludo
> Date: 2009-05-11 19:57:42 + (Mon, 11 May 2009)
> New Revision: 1
>
> You can view the changes in this commit at:
>https://svn.nixos.org/viewvc/nix?rev=1&view=rev
>
> Modified:
>nixpkgs/trunk/pkgs/development/libraries/SDL/default.ni
> 2) To solve your problem you can concatenate the path with a string.
> Unfortunately, I am not sure this will recompile the package if its
> patch changes.
>
> patches = [ (./ + "/${version}.patch") ];
patches = [ (./. + "/${version}.patch") ];
is a more concise form of what I was doing bef
