[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sudo error

From: Live System User
Subject: Re: sudo error
Date: Mon, 19 Nov 2018 00:30:03 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)


Michael Albinus <address@hidden> writes:

> Live System User <address@hidden> writes:
>> Hi,
> Hi,
>>   "emacs -Q" works fine with the already opened file...
>>    ...and with a minimal config:
>>     So what can it be?
> As said in my first analysis, Tramp stumbled over the not-remote-file
> "~". Maybe some file abbreviation is at work? Don't know, it depends on
> whatever package has been loaded silently in your default config.

  I tried again, this time using the ssh method.

  This works:

      C-x C-r /ssh::/tmp/malb.txt

  in thar it opens the file in readonly mode.

Attachment: ssh-info.txt
Description: ssh attempt #1

Attachment: sudo-2.txt
Description: ssh repeat attempt #2

  However, I still see the "Not a Tramp file name" messages, even
  for the SAVEHIST file ~/.emacs.d/savehist".

  I did this twice -- the results in the files ssh-ibfo.txt and
  ssh-info2.txt, respectively (see attachments).

  Both logfiles appears to have mostly the same results except that
  the second invocation uses the already-created shared connection
  and complains about "savehist" mode.  It doesn't complain the
  secind tume.

  Bur both times it complains about Not a Tramp file name: "~"

  So why is "savehist mode" getting in the way of TRAMP?

  And why does the ssh method "work" (even though it causes a
  "Not a Tramp file name" message to be emitted) whereas the
  sudo method doesn't work at all?

  Can the sudo method be made to protect itself againts "savehist"
  mode similiar to how the ssh method deals with it and allows
  the ssh method to work?


>>     Thanks.
> Best regards, Michael.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]