unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
Cc: 39389@debbugs.gnu.org
Subject: bug#39389: 27.0.60; A couple of bugs messing with minibuffer completion of /sudo::
Date: Sat, 08 Feb 2020 19:36:47 +0100	[thread overview]
Message-ID: <87eev553k0.fsf@gmx.de> (raw)
In-Reply-To: <CAKDRQS5SLhP4K8KgL2AA3taE=0PorhRBJB00pDsHYS=-7g+8XA@mail.gmail.com> (Jimmy Yuen Ho Wong's message of "Sat, 8 Feb 2020 13:03:47 +0000")

Jimmy Yuen Ho Wong <wyuenho@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.





  reply	other threads:[~2020-02-08 18:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02 14:50 bug#39389: 27.0.60; A couple of bugs messing with minibuffer completion of /sudo:: Jimmy Yuen Ho Wong
2020-02-02 15:47 ` Michael Albinus
2020-02-02 18:05   ` Jimmy Yuen Ho Wong
2020-02-02 18:14     ` Michael Albinus
2020-02-02 18:30       ` Jimmy Yuen Ho Wong
2020-02-02 20:11         ` Michael Albinus
2020-02-05 13:31           ` Jimmy Yuen Ho Wong
2020-02-05 14:39             ` Michael Albinus
2020-02-08 13:03               ` Jimmy Yuen Ho Wong
2020-02-08 18:36                 ` Michael Albinus [this message]
2020-02-09  5:22                   ` Jimmy Yuen Ho Wong
2020-02-09 23:44                   ` Jimmy Yuen Ho Wong
2020-02-10  0:16                     ` Jimmy Yuen Ho Wong
2020-02-10  9:23                       ` Michael Albinus
2020-02-10  9:18                     ` Michael Albinus
2020-02-10 21:00                       ` Jimmy Yuen Ho Wong
2020-02-10 21:06                       ` Jimmy Yuen Ho Wong
2020-02-11  8:56                         ` Michael Albinus
2020-02-16 19:30                           ` Michael Albinus

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87eev553k0.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=39389@debbugs.gnu.org \
    --cc=wyuenho@gmail.com \
    /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/emacs.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).