[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt
|
From: |
Eli Zaretskii |
|
Subject: |
bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob |
|
Date: |
Fri, 22 Feb 2019 10:37:00 +0200 |
> From: Alex Branham <alex.branham@gmail.com>
> Date: Thu, 21 Feb 2019 10:32:16 -0600
>
> Is this patch OK for Emacs? Or should we figure it out downstream?
Can you explain how having comint-prompt-read-only interferes with
interrupt-process in this case? I don't think I understand the
connection, and neither this bug report nor the ESS issue do, AFAICT.
Thanks.
- bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob, Alex Branham, 2019/02/21
- bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob,
Eli Zaretskii <=
- bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob, Alex Branham, 2019/02/22
- bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob, Eli Zaretskii, 2019/02/23
- bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob, Alex Branham, 2019/02/23
- bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob, Eli Zaretskii, 2019/02/23
- bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob, Alex Branham, 2019/02/24
- bug#33975: [PATCH] inhibit read-only text properties in comint-interrupt-subjob, Alex Branham, 2019/02/24