GNU bug report logs - #39389
27.0.60; A couple of bugs messing with minibuffer completion of /sudo::

Previous Next

Package: emacs;

Reported by: Jimmy Yuen Ho Wong <wyuenho <at> gmail.com>

Date: Sun, 2 Feb 2020 14:52:02 UTC

Severity: normal

Tags: patch

Found in version 27.0.60

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


Message #32 received at 39389 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Jimmy Yuen Ho Wong <wyuenho <at> gmail.com>
Cc: 39389 <at> debbugs.gnu.org
Subject: Re: bug#39389: 27.0.60; A couple of bugs messing with minibuffer
 completion of /sudo::
Date: Sat, 08 Feb 2020 19:36:47 +0100
Jimmy Yuen Ho Wong <wyuenho <at> gmail.com> writes:

Hi,

> For bug 2 and 3, the author said `file-remote-p` might have triggered
> some weird code paths that triggered this bug. I don't know how to
> edebug further as `redisplay_internal` keeps calling it. Do you know
> how to debug it?
>
> https://github.com/purcell/exec-path-from-shell/issues/95#issuecomment-582629738

I doubt that file-remote-p is guilty. This function is designed to *not*
work on the remote side, but check the syntax of a file name only.

However, I've downloaded the package exec-path-from-shell from
MELPA. Reading the code, I have serious doubst it will cooperate with
Tramp. It's idea is to analyze the *local* shell, and apply actions over
the shell. But the *local* shell doesn't matter for remote files, so it
is completely useless. I'd recommend NOT to use exec-path-from-shell for
remote files.

If you want to know mor details what happens with Tramp, you might
analyze the function calls. Evaluate

--8<---------------cut here---------------start------------->8---
(require 'trace)
(dolist (elt (all-completions "tramp-" obarray 'functionp))
  (trace-function-background (intern elt)))
(untrace-function 'tramp-read-passwd)
--8<---------------cut here---------------end--------------->8---

Then run your test. The buffer *trace-output* contains the output from
the function call traces. You might show it here, maybe I can find
something more about the problem.

Best regards, Michael.




This bug report was last modified 5 years and 174 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.