GNU bug report logs - #36532
tramp-signal-hook-function: Text is read-only: "nil"

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36532 in the body.
You can then email your comments to 36532 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: Fritz Stelzer <brotzeitmacher <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: tramp-signal-hook-function: Text is read-only: "nil"
Date: Sat, 6 Jul 2019 22:43:51 +0200

[Message part 1 (text/plain, inline)]

When I use `async-shell-command` on a remote host I get this error if
there's already the
*Async Shell Command* buffer. When there's a running process and I confirm
to kill the process, it works. It seems to work correctly for
`shell-command`.
I didn't have any issues while trying this locally. I'm on d07dd64fd0.

[Message part 2 (text/html, inline)]

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

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Fritz Stelzer <brotzeitmacher <at> gmail.com>
Cc: 36532 <at> debbugs.gnu.org
Subject: Re: bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
Date: Sun, 07 Jul 2019 11:20:43 +0200

Fritz Stelzer <brotzeitmacher <at> gmail.com> writes:

Hi Fritz,

> When I use `async-shell-command` on a remote host I get this error if
> there's already the
> *Async Shell Command* buffer. When there's a running process and I
> confirm to kill the process, it works. It seems to work correctly for
> `shell-command`.
> I didn't have any issues while trying this locally. I'm on d07dd64fd0.

I cannot reproduce it locally. Scenario:

- emacs -Q /ssh::

- M-& sleep 600

- M-& sleep 600

I get the message "A command is running in the default buffer.  Use a
new buffer? (yes or no) " If I enter "yes", it opens a second buffer
*Async Shell Command*<2>. If I enter "no", there is the error message
"tramp-error: Shell command in progress" in the *Messages* buffer, which
is likely OK.

The same happens if I run it on a local buffer, but in the "no" case the
error message is "shell-command: Shell command in progress".

Arguably, there shouldn't be an error but a user error, but I don't see
anything else. What's the difference in your use case?

If you still see something strange, could you run your scenario with
tramp-verbose set to 10, and send us the Tramp debug buffer?

Best regards, Michael.

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

From: Pip Cet <pipcet <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: Fritz Stelzer <brotzeitmacher <at> gmail.com>, 36532 <at> debbugs.gnu.org
Subject: Re: bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
Date: Sun, 7 Jul 2019 11:59:04 +0000

On Sun, Jul 7, 2019 at 9:21 AM Michael Albinus <michael.albinus <at> gmx.de> wrote:
> Fritz Stelzer <brotzeitmacher <at> gmail.com> writes:
> > When I use `async-shell-command` on a remote host I get this error if
> > there's already the
> > *Async Shell Command* buffer. When there's a running process and I
> > confirm to kill the process, it works. It seems to work correctly for
> > `shell-command`.
> > I didn't have any issues while trying this locally. I'm on d07dd64fd0.

Is it possible this is bug #36447? Fritz, could you try one of the
fixes there if you still have the problem?

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

From: Fritz Stelzer <brotzeitmacher <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 36532 <at> debbugs.gnu.org
Subject: Re: bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
Date: Tue, 9 Jul 2019 18:08:28 +0200

[Message part 1 (text/plain, inline)]

Ah sorry, I forgot to use emacs -Q again. I guess I have to find the issue
myself.

On Sun, Jul 7, 2019 at 11:20 AM Michael Albinus <michael.albinus <at> gmx.de>
wrote:

> Fritz Stelzer <brotzeitmacher <at> gmail.com> writes:
>
> Hi Fritz,
>
> > When I use `async-shell-command` on a remote host I get this error if
> > there's already the
> > *Async Shell Command* buffer. When there's a running process and I
> > confirm to kill the process, it works. It seems to work correctly for
> > `shell-command`.
> > I didn't have any issues while trying this locally. I'm on d07dd64fd0.
>
> I cannot reproduce it locally. Scenario:
>
> - emacs -Q /ssh::
>
> - M-& sleep 600
>
> - M-& sleep 600
>
> I get the message "A command is running in the default buffer.  Use a
> new buffer? (yes or no) " If I enter "yes", it opens a second buffer
> *Async Shell Command*<2>. If I enter "no", there is the error message
> "tramp-error: Shell command in progress" in the *Messages* buffer, which
> is likely OK.
>
> The same happens if I run it on a local buffer, but in the "no" case the
> error message is "shell-command: Shell command in progress".
>
> Arguably, there shouldn't be an error but a user error, but I don't see
> anything else. What's the difference in your use case?
>
> If you still see something strange, could you run your scenario with
> tramp-verbose set to 10, and send us the Tramp debug buffer?
>
> Best regards, Michael.
>

[Message part 2 (text/html, inline)]

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

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Fritz Stelzer <brotzeitmacher <at> gmail.com>
Cc: 36532 <at> debbugs.gnu.org
Subject: Re: bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
Date: Tue, 09 Jul 2019 18:25:03 +0200

Fritz Stelzer <brotzeitmacher <at> gmail.com> writes:

Hi Fritz,

> Ah sorry, I forgot to use emacs -Q again. I guess I have to find the
> issue myself.

Does this mean the problem doesn't happen in case of "emacs -Q"? In
that case, I would like to close the bug.

Best regards, Michael.

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

From: Fritz Stelzer <brotzeitmacher <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 36532 <at> debbugs.gnu.org
Subject: Re: bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
Date: Wed, 10 Jul 2019 23:13:53 +0200

[Message part 1 (text/plain, inline)]

Yes, it does. Thanks for the fast reply!

On Tue, Jul 9, 2019 at 6:25 PM Michael Albinus <michael.albinus <at> gmx.de>
wrote:

> Fritz Stelzer <brotzeitmacher <at> gmail.com> writes:
>
> Hi Fritz,
>
> > Ah sorry, I forgot to use emacs -Q again. I guess I have to find the
> > issue myself.
>
> Does this mean the problem doesn't happen in case of "emacs -Q"? In
> that case, I would like to close the bug.
>
> Best regards, Michael.
>

[Message part 2 (text/html, inline)]

Previous Next

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