unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: the_wurfkreuz <the_wurfkreuz@proton.me>
Cc: 72117@debbugs.gnu.org
Subject: bug#72117: Command doesn't execute correctly in eshell
Date: Tue, 16 Jul 2024 19:09:32 -0700	[thread overview]
Message-ID: <CANh=_JEfR-H5NFBwpG-XAG-LQrrJ3HSVqouJnDxe-2dYO=AsRg@mail.gmail.com> (raw)
In-Reply-To: <uDv8zx2ccT4dsHYBueowwgc6Hjuz4gs3wLRNNOXllaD4ifNUqW2-7eEYYJDjsG5VzBWGHQGoIJ1aFnbQxMLoacZR71w8v11rIb7GTfhQuus=@proton.me>

(Don't forget to Reply All so that Debbugs is CCed in your message, or
else the tracker won't see your messages.)

On Tue, Jul 16, 2024 at 2:14 AM the_wurfkreuz <the_wurfkreuz@proton.me> wrote:
>
> I updated Emacs and used your latest patch. The problem with pipe is fixed as far as i can understand, but my original problem with executing the command through tramp (eshell/sudo) is still there, though it's elusive and hard to reproduce. Right now, i can't reproduce it launching bare Emacs (emacs -Q). And with my current config i was getting it around 50/50 of the time. When i got it, i had this message: 'error in process filter: Forbidden reentrant call of Tramp'.

After testing some more locally, I notice that too. Digging further,
this problem is actually multifaceted, and fixing all the different
issues I've uncovered would be too risky for Emacs 30. Does the first
patch I posted work for you? That's a lot simpler, and should be safe
enough for Emacs 30; then I can make more extensive fixes for Emacs
31.

(The "Forbidden reentrant call of Tramp" is likely occurring when
calling 'signal-process' on the "lsof" command, which could happen if
some Tramp code is above us in the stack; in that case,
'signal-process' would reenter Tramp code, and then Tramp bails out
just to be safe.)





  parent reply	other threads:[~2024-07-17  2:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-14 19:33 bug#72117: Command doesn't execute correctly in eshell the_wurfkreuz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-15  1:01 ` Jim Porter
2024-07-16  3:09   ` Jim Porter
     [not found]     ` <uDv8zx2ccT4dsHYBueowwgc6Hjuz4gs3wLRNNOXllaD4ifNUqW2-7eEYYJDjsG5VzBWGHQGoIJ1aFnbQxMLoacZR71w8v11rIb7GTfhQuus=@proton.me>
2024-07-17  2:09       ` Jim Porter [this message]
2024-07-18  5:05         ` Jim Porter
2024-07-18  9:31           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-18 15:38             ` Jim Porter
2024-07-18 16:49               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-18 18:26                 ` Jim Porter
2024-07-27  5:18   ` Jim Porter
2024-07-27  6:40     ` Eli Zaretskii
2024-07-27 19:14       ` Jim Porter
2024-07-28  7:59         ` Jim Porter
2024-07-28 16:21           ` Jim Porter

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='CANh=_JEfR-H5NFBwpG-XAG-LQrrJ3HSVqouJnDxe-2dYO=AsRg@mail.gmail.com' \
    --to=jporterbugs@gmail.com \
    --cc=72117@debbugs.gnu.org \
    --cc=the_wurfkreuz@proton.me \
    /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).