[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it
From: |
Eli Zaretskii |
Subject: |
bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it |
Date: |
Wed, 02 Apr 2014 23:22:08 +0300 |
> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
> Cc: Nicolas Richard <theonewiththeevillook@yahoo.fr>, 17170@debbugs.gnu.org
> Date: Wed, 02 Apr 2014 19:57:24 +0200
>
> > Do you have debug-on-error set non-nil or something?
>
> It is set to t.
I'm guessing that keeping it at nil will allow you to continue from
that error, instead of being stuck in an endless loop of recursive
editing.
- bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it, Nicolas Richard, 2014/04/02
- bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it, Eli Zaretskii, 2014/04/02
- bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it, Nicolas Richard, 2014/04/06
- bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it, Eli Zaretskii, 2014/04/06
- bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it, Nicolas Richard, 2014/04/06
- bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it, Eli Zaretskii, 2014/04/06
- bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it, Eli Zaretskii, 2014/04/06