ea why that is? It seems kind of unusual for nixos-rebuild
> switch to not change things like that...
>
> On Tue, Apr 4, 2017 at 6:28 PM, ben...@gmail.com wrote:
>
>> Worth noting: Running `nixos-rebuild switch` is insufficient to make
>> this fix take effect. You may need
Are you talking about the desktop app launchers that show up in the
kde/gnome/whatever application menus? Because yeah, that totally happens.
The issue is that chrome writes the app's .destop file (at
~/.local/share/applications/chrome-.desktop) with the full
/nix/store path to the non-wrapped goo
Worth noting: Running `nixos-rebuild switch` is insufficient to make
this fix take effect. You may need to run `systemctl restart
docker.socket` or reboot before the permissions on /run/docker.sock
will be corrected.
On Mon, Apr 3, 2017 at 8:19 PM, Graham Christensen wrote:
> -BEGIN PGP SIG
Your messages to this list are non-constructive, needlessly inflammatory,
and combative. Several people have pointed out that there is interest in
supporting alternate init systems with Nix, and nobody is attacking you for
preferring not to use systemd. Please stop trying to provoke a flamewar.
AFAIK it currently does not. And I agree, it would be a better user
experience if that were the case.
On Sun, Mar 19, 2017 at 4:06 PM, Bjørn Forsman wrote:
> On 19 March 2017 at 20:50, ben...@gmail.com wrote:
>> That results in just a `vim` executable that does not load any user
>
ional linux distribution.
On Sun, Mar 19, 2017 at 3:40 PM, Vladimír Čunát wrote:
> On 03/19/2017 08:33 PM, ben...@gmail.com wrote:
>> I keep wanting vim_configurable to produce a "normal" vim package
>> (including executables for gvim, xxd, vimdiff, etc) that has no
>>
Ha, you beat me to the post by like ten seconds! I see you use the
same trick with sourcing ~/.vimrc in vim_configurable - now I am
wondering, does anybody out there use it the way it appears it's
intended to be used?
I keep wanting vim_configurable to produce a "normal" vim package
(including ex
The answer is somewhat more complex than one might expect, but there is
documentation about how to build vim along with various plugins at
https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/vim.md
Here is an example ~/.nixpkgs/config.nix with an example of what I think
you are l
My approach is quite similar to Jookia's. I also point nixpkgs at a
remote tarball from a github branch that I control, which takes the
place of using nix-channel, and set nixos-config relative to
config.networking.hostName. With this setup, I don't need any
symlinks, nor custom imports in ~/.nix
Thanks! I've applied your patch in
https://github.com/NixOS/nixpkgs/pull/22723
On Sun, Feb 12, 2017 at 6:14 PM, Karn Kallio
wrote:
>
> The sddm must be handled separately (as with kdm) in the xsession start
> script because it treats the Exec line in the .desktop file as a
> parameter and not a
On Sat, Feb 11, 2017 at 11:36 AM, Vladimír Čunát wrote:
> On 02/11/2017 05:22 PM, Graham Christensen wrote:
> > How far can we go for 17.03?
>
> I'd personally drop any support for it in 17.03, *including* security
> updates. Whether we do that as removal, brokenness or something seems a
> relat
People are eager to fix bugs in the manual, but it would be a lot more
helpful if you could describe specifically what you've run into. I'm sorry
that you had a bad experience with NixOS, but your message is not
particularly constructive as it stands.
On Thu, Apr 14, 2016 at 2:32 AM john delport
I would love to see a workflow involving a merge queue, where normally
humans should never push directly to master nor click merge on pull
requests, but instead:
1. developer opens pull request
2. travis runs tests, posts results as usual
3. someone with approval/commit rights comments: "nixbot: O
I agree, and feel that killing the wiki would be a mistake. The existing
wiki could really use some clean up and better structure, but its existence
was a crucial factor in helping me get started with Nix and I imagine the
same is true for many other users.
http://wiki.archlinux.org is an excelle
I like that one a lot too; it is a lovely refinement of the current logo.
On Tue, Sep 8, 2015 at 2:06 AM Guillaume Maudoux (Layus)
wrote:
> Tim has invested some time in making great logos, and everybody seems to
> like the hex-half version.
> It would be too sad to loose his job, so what is the
In that case, you can simply set priorities on the packages you want to
control. There are some helper functions for that, so you can have
something like:
with import {};
buildEnv {
name = "myEnv";
ignoreCollisions = true;
paths = [
(lib.lowPrio coreutils)
procps
];
}
(that's wh
16 matches
Mail list logo
