* bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
@ 2019-07-06 20:43 Fritz Stelzer
2019-07-07 9:20 ` Michael Albinus
0 siblings, 1 reply; 6+ messages in thread
From: Fritz Stelzer @ 2019-07-06 20:43 UTC (permalink / raw)
To: 36532
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 359 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
2019-07-06 20:43 bug#36532: tramp-signal-hook-function: Text is read-only: "nil" Fritz Stelzer
@ 2019-07-07 9:20 ` Michael Albinus
2019-07-07 11:59 ` Pip Cet
2019-07-09 16:08 ` Fritz Stelzer
0 siblings, 2 replies; 6+ messages in thread
From: Michael Albinus @ 2019-07-07 9:20 UTC (permalink / raw)
To: Fritz Stelzer; +Cc: 36532
Fritz Stelzer <brotzeitmacher@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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
2019-07-07 9:20 ` Michael Albinus
@ 2019-07-07 11:59 ` Pip Cet
2019-07-09 16:08 ` Fritz Stelzer
1 sibling, 0 replies; 6+ messages in thread
From: Pip Cet @ 2019-07-07 11:59 UTC (permalink / raw)
To: Michael Albinus; +Cc: Fritz Stelzer, 36532
On Sun, Jul 7, 2019 at 9:21 AM Michael Albinus <michael.albinus@gmx.de> wrote:
> Fritz Stelzer <brotzeitmacher@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?
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
2019-07-07 9:20 ` Michael Albinus
2019-07-07 11:59 ` Pip Cet
@ 2019-07-09 16:08 ` Fritz Stelzer
2019-07-09 16:25 ` Michael Albinus
1 sibling, 1 reply; 6+ messages in thread
From: Fritz Stelzer @ 2019-07-09 16:08 UTC (permalink / raw)
To: Michael Albinus; +Cc: 36532
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
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@gmx.de>
wrote:
> Fritz Stelzer <brotzeitmacher@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.
>
[-- Attachment #2: Type: text/html, Size: 2013 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
2019-07-09 16:08 ` Fritz Stelzer
@ 2019-07-09 16:25 ` Michael Albinus
2019-07-10 21:13 ` Fritz Stelzer
0 siblings, 1 reply; 6+ messages in thread
From: Michael Albinus @ 2019-07-09 16:25 UTC (permalink / raw)
To: Fritz Stelzer; +Cc: 36532
Fritz Stelzer <brotzeitmacher@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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#36532: tramp-signal-hook-function: Text is read-only: "nil"
2019-07-09 16:25 ` Michael Albinus
@ 2019-07-10 21:13 ` Fritz Stelzer
0 siblings, 0 replies; 6+ messages in thread
From: Fritz Stelzer @ 2019-07-10 21:13 UTC (permalink / raw)
To: Michael Albinus; +Cc: 36532
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Yes, it does. Thanks for the fast reply!
On Tue, Jul 9, 2019 at 6:25 PM Michael Albinus <michael.albinus@gmx.de>
wrote:
> Fritz Stelzer <brotzeitmacher@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.
>
[-- Attachment #2: Type: text/html, Size: 834 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-07-10 21:13 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-06 20:43 bug#36532: tramp-signal-hook-function: Text is read-only: "nil" Fritz Stelzer
2019-07-07 9:20 ` Michael Albinus
2019-07-07 11:59 ` Pip Cet
2019-07-09 16:08 ` Fritz Stelzer
2019-07-09 16:25 ` Michael Albinus
2019-07-10 21:13 ` Fritz Stelzer
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).