Re: Using tramp with guixsd install image

[Divan Santana]

Alex Kost <address@hidden> writes:

> Divan Santana (2017-06-30 22:15 +0200) wrote:
>
>> Hi,
>>
>> Trying to use my emacs (on arch linux) with the guixsd system from the
>> 0.13 image and ssh-daemon. By image, this is a fresh VM booted
>> guixsd-usb-install-0.13.0.x86_64-linux and about to install guixsd .
>>
>> This Used to work with 0.12 image.
>>
>> Now I have this set
>>
>>   ;; ;; TRAMP and guix settings
>>   (setq tramp-default-method "scp")
>>   ;; https://lists.gnu.org/archive/html/help-guix/2016-10/msg00049.html
>>   (setq tramp-remote-path
>>         (append tramp-remote-path
>>                 '("~/.guix-profile/bin" "~/.guix-profile/sbin"
>>                   "/run/current-system/profile/bin"
>>                   "/run/current-system/profile/sbin")))
>
> With this ^^^ your additional paths are "shadowed" by the default
> value of 'tramp-remote-path'.  Try to make it reverse:
>
>    (setq tramp-remote-path
>          (append '("~/.guix-profile/bin" "~/.guix-profile/sbin"
>                    "/run/current-system/profile/bin"
>                    "/run/current-system/profile/sbin")
>                  tramp-remote-path))

The above does make sense. I've tried it your suggested way and
unfortunately I'm getting the same results. For some reason my emacs
tramp is looking for /bin/sh still and has the same initial error
reported.

> However I don't think you need to set all these paths manually.
>
> The different behavior between 0.12 and 0.13 may be caused by this
> commit:
>
>   
> http://git.savannah.gnu.org/cgit/guix.git/commit/?id=dc7010911dd3285fe9089352e92c77501595d100
>
> i.e. your problem may occur because 'tramp-default-remote-path' is the
> first element of 'tramp-remote-path' variable now.

I think this wouldn't affect me as my emacs is from arch linux repositories?

>> How can one configure tramp to work without the above hack?
>
> I don't know if it will help you or not, but here is the setting I have
> in my emacs config, which works for me for years:
>
> (with-eval-after-load 'tramp-sh
>   (push 'tramp-own-remote-path tramp-remote-path))

The above didn't work for me either.