c-g in emacs locked in other terminal?

c-g in emacs locked in other terminal?

[joakim]

Hello,

I use the emacs feature to attach to a running emacs server in multiple
clients a lot. Sometimes I do m-x in one of the terminals, forget about
it, and then try to use emacs from some of the other terminals, which are
now unresponsive. If the original terminal where i did an unfinished m-x
is not readily available, its pretty hard to get out of this state.

I've been using this feature since it was called mtty-emacs, but I've
never figured out the correct procedure to get out of it, except
attaching to the original terminal, and doing c-g there.

Any hints? The most convenient would be to configure c-g to just break
all terminals, if possible.
-- 
Joakim Verona
joakim@verona.se

Re: c-g in emacs locked in other terminal?

[Po Lu]

joakim@verona.se writes:

> I use the emacs feature to attach to a running emacs server in multiple
> clients a lot. Sometimes I do m-x in one of the terminals, forget about
> it, and then try to use emacs from some of the other terminals, which are
> now unresponsive. If the original terminal where i did an unfinished m-x
> is not readily available, its pretty hard to get out of this state.
>
> I've been using this feature since it was called mtty-emacs, but I've
> never figured out the correct procedure to get out of it, except
> attaching to the original terminal, and doing c-g there.
>
> Any hints? The most convenient would be to configure c-g to just break
> all terminals, if possible.

Input is not handled from other terminals during a recursive edit (or
more precisely, inside single-keyboard mode, which is turned on then and
in some other similar situations.)

I don't understand why it has to work that way, but it's a known problem
with no fix.  See admin/notes/multi-tty.

Re: c-g in emacs locked in other terminal?

[joakim]

Po Lu <luangruo@yahoo.com> writes:

> joakim@verona.se writes:
>
>> I use the emacs feature to attach to a running emacs server in multiple
>> clients a lot. Sometimes I do m-x in one of the terminals, forget about
>> it, and then try to use emacs from some of the other terminals, which are
>> now unresponsive. If the original terminal where i did an unfinished m-x
>> is not readily available, its pretty hard to get out of this state.
>>
>> I've been using this feature since it was called mtty-emacs, but I've
>> never figured out the correct procedure to get out of it, except
>> attaching to the original terminal, and doing c-g there.
>>
>> Any hints? The most convenient would be to configure c-g to just break
>> all terminals, if possible.
>
> Input is not handled from other terminals during a recursive edit (or
> more precisely, inside single-keyboard mode, which is turned on then and
> in some other similar situations.)
>
> I don't understand why it has to work that way, but it's a known problem
> with no fix.  See admin/notes/multi-tty.

Thanks!
>
>
-- 
Joakim Verona
joakim@verona.se

Re: c-g in emacs locked in other terminal?

[andrés ramírez]

Hi. Joakim.

>>>>> "joakim" == joakim  <joakim@verona.se> writes:

    joakim> Hello, I use the emacs feature to attach to a running emacs server in multiple clients a
    joakim> lot. Sometimes I do m-x in one of the terminals, forget about it, and then try to use
    joakim> emacs from some of the other terminals, which are now unresponsive. If the original
    joakim> terminal where i did an unfinished m-x is not readily available, its pretty hard to get
    joakim> out of this state.

I have this line on my .bashrc that helps me on that situation:
--8<---------------cut here---------------start------------->8---
alias myfixem="emacsclient --eval \" (run-at-time \\\"1\\\" nil  #'kill-buffer \\\"*Backtrace*\\\") \""
--8<---------------cut here---------------end--------------->8---

Best Regards

Re: c-g in emacs locked in other terminal?

[joakim]

andrés ramírez <rrandresf@hotmail.com> writes:

> Hi. Joakim.
>
>>>>>> "joakim" == joakim  <joakim@verona.se> writes:
>
>     joakim> Hello, I use the emacs feature to attach to a running emacs server in multiple clients a
>     joakim> lot. Sometimes I do m-x in one of the terminals, forget about it, and then try to use
>     joakim> emacs from some of the other terminals, which are now unresponsive. If the original
>     joakim> terminal where i did an unfinished m-x is not readily available, its pretty hard to get
>     joakim> out of this state.
>
> I have this line on my .bashrc that helps me on that situation:
>
> alias myfixem="emacsclient --eval \" (run-at-time \\\"1\\\" nil  #'kill-buffer \\\"*Backtrace*\\\") \""
>
> Best Regards

Thanks! I will test this

>
>
-- 
Joakim Verona
joakim@verona.se