Re: [Nix-dev] paths in user's i3 configs broken by upgrade

2017-04-05 Thread Guillaume Maudoux (Layus)
On 05/04/17 03:46, Profpatsch wrote: On 17-04-03 04:25pm, Mark Gardner wrote: Instead of: bindsym $mod+d exec /nix/store/04sx6lx7hssid7a6iwdbdvxbkp25xsx1-dmenu-4.6/bin/dmenu_run I think it should be to be: bindsym $mod+d exec /run/current-system/sw/bin/dmenu_run The problem with /

Re: [Nix-dev] paths in user's i3 configs broken by upgrade

2017-04-04 Thread Profpatsch
On 17-04-03 04:25pm, Mark Gardner wrote: > Instead of: > > bindsym $mod+d exec > /nix/store/04sx6lx7hssid7a6iwdbdvxbkp25xsx1-dmenu-4.6/bin/dmenu_run > > I think it should be to be: > > bindsym $mod+d exec /run/current-system/sw/bin/dmenu_run The problem with /run/current-system is that

[Nix-dev] paths in user's i3 configs broken by upgrade

2017-04-03 Thread Mark Gardner
I just upgraded from an early 17.03 beta to 17.03 and the $mod+d key combination for invoking dmenu no longer works in i3. The problem is that the paths to dmenu in the ${i3}/etc/config* files are hard coded when the config files are created and propagated to the user's .config/i3/config file by i