[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#30182: Update
From: |
martin rudalics |
Subject: |
bug#30182: Update |
Date: |
Fri, 02 Feb 2018 09:37:26 +0100 |
> > So I'm still unsure what is going on here. But if indeed the above
> > scenario somehow ends up calling Lisp from the async redisplay,
> > wrapping the call to Fcopy_sequence in timer_check with block_input
> > and unblock_input should solve the problem, right?
>
> But we can't do that, right? Users should be able to cancel it.
I misread your lines. Wrapping that call should indeed solve the
problem.
martin
- bug#30182: Update, martin rudalics, 2018/02/01
- bug#30182: Update, Eli Zaretskii, 2018/02/01
- bug#30182: Update, Noam Postavsky, 2018/02/02
- bug#30182: Update, Eli Zaretskii, 2018/02/02
- bug#30182: Update, martin rudalics, 2018/02/03
- bug#30182: Update, Eli Zaretskii, 2018/02/03
- bug#30182: Update, martin rudalics, 2018/02/04
- bug#30182: Update, Eli Zaretskii, 2018/02/04
bug#30182: Update, martin rudalics, 2018/02/02
- bug#30182: Update,
martin rudalics <=
- bug#30182: Update, Eli Zaretskii, 2018/02/02
- bug#30182: Update, martin rudalics, 2018/02/03
- bug#30182: Update, Eli Zaretskii, 2018/02/03
- bug#30182: Update, martin rudalics, 2018/02/04
- bug#30182: Update, Eli Zaretskii, 2018/02/04
- bug#30182: Update, martin rudalics, 2018/02/06
- bug#30182: Update, martin rudalics, 2018/02/10