unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Iurie Marian <marian.iurie@gmail.com>
Cc: 71709@debbugs.gnu.org
Subject: bug#71709: Fix recent change in tramp-sh-handle-make-process
Date: Sat, 22 Jun 2024 19:05:14 +0200	[thread overview]
Message-ID: <87v820q56d.fsf@gmx.de> (raw)
In-Reply-To: <CAP+jDP5ZH4JgkFzczMKmnqWebq6msg07BDUEGOy2ryDZyeMCXw@mail.gmail.com> (Iurie Marian's message of "Sat, 22 Jun 2024 18:52:01 +0200")

Iurie Marian <marian.iurie@gmail.com> writes:

Hi Iurie,

> Unfortunately, the patch doesn't help.
> By the way, this is what I noticed:
> * the issue seems to occur more often in a docker container
> * over /ssh it is working well, or at least it never occurred
> * the temporary buffers like ~/tmp/tramp.J0RZDc~ are actually created on remote
> * after repetitive tests I noticed that it doesn't reproduce anymore
> and I added a line to print the default-directory right before
> `make-process` for stderr: ~lisp/net/tramp-sh.el:3057~
>   - when it fails, the default-directory is on local host
>   - when it succeeds - it's on remote (where I guess it finds that
> temporary file)

But this was exactly the change I have sent to you: preserve proper default-directory.

> * on emacs restart it starts reproducing again
> * once it starts working, it never reproduces again until emacs restart
>
> It looks like it has something to do with `stderr` process execution
> environment.

Yes. Did you apply the change as I have said? That means

- Patch tramp.el inside the emacs tree
- Remove all compiled Tramp files, like 'rm lisp/net/tramp*.elc'
- Recompile EWmacs by calling 'make'.

Best regards, Michael.





  reply	other threads:[~2024-06-22 17:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 18:12 bug#71709: Fix recent change in tramp-sh-handle-make-process Iurie Marian
2024-06-21 19:21 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-21 21:09   ` Iurie Marian
2024-06-22  7:31     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22  9:10       ` Iurie Marian
2024-06-22  9:18         ` Iurie Marian
2024-06-22  9:23           ` Iurie Marian
2024-06-22 11:18         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 12:02           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 16:52             ` Iurie Marian
2024-06-22 17:05               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-22 17:27                 ` Iurie Marian
2024-06-22 17:54                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87v820q56d.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71709@debbugs.gnu.org \
    --cc=marian.iurie@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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).