unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Remco van 't Veer <remco@remworks.net>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 55443@debbugs.gnu.org
Subject: bug#55443: emacs-28.1: tramp sudo broken
Date: Thu, 19 May 2022 16:55:34 +0200	[thread overview]
Message-ID: <87h75lbmhl.fsf@remworks.net> (raw)
In-Reply-To: <874k1l39r9.fsf@jpoiret.xyz>

2022/05/19 15:57, Josselin Poiret:

> What I personally use is described at [1], and fixed this issue I had
> when I switched to emacs-next.
>
> [1] https://yhetil.org/guix/87czjsmif0.fsf@jpoiret.xyz/

Thanks!  Your workaround works.  Here's my slightly tweaked version
(inspired by the post by Max Brieiev):

  (connection-local-set-profile-variables
    'guix-system
    '((tramp-remote-path . (tramp-own-remote-path))))

  (connection-local-set-profiles
    `(:application tramp :protocol "sudo" :machine ,(system-name))
    'guix-system))

I do agree with Maxime Devos in the same thread, ideally tramp sudo
should just work on guix.




  reply	other threads:[~2022-05-19 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  6:27 bug#55443: emacs-28.1: tramp sudo broken Remco van 't Veer
2022-05-19 12:46 ` benoit
2022-05-19 13:57 ` Josselin Poiret via Bug reports for GNU Guix
2022-05-19 14:55   ` Remco van 't Veer [this message]
2022-06-22  1:53 ` bug#55443: [PATCH] gnu: emacs: Fix source snippet John Kehayias via Bug reports for GNU Guix
2022-06-22 14:41   ` John Kehayias via Bug reports for GNU Guix
2022-06-22 19:47   ` Liliana Marie Prikler
2022-06-22 20:06     ` John Kehayias via Bug reports for GNU Guix
2022-06-23  5:26       ` Liliana Marie Prikler
     [not found] ` <handler.55443.D55443.165592726026934.notifdone@debbugs.gnu.org>
2022-06-25 14:57   ` bug#55443: closed (Re: [PATCH] gnu: emacs: Fix source snippet.) Remco van 't Veer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h75lbmhl.fsf@remworks.net \
    --to=remco@remworks.net \
    --cc=55443@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).