[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mouse-drag-and-drop-region
From: |
martin rudalics |
Subject: |
Re: mouse-drag-and-drop-region |
Date: |
Tue, 14 Nov 2017 19:29:33 +0100 |
>> (8) Read-only text should be handled. An attempt to drop text into a
>> read-only area should be signalled to the user. An attempt to cut
>> text from a read-only text/buffer should be signalled as well.
>
> For the latter, we copy text instead (cf C-w in read-only text). So I
> think this feature should behave similarly, at least by default.
I just noticed that the code does use ‘kill-region’ already. This has
the side-effect of putting the text into the kill ring, something which
should be documented at least. But I think the code should rather use
‘delete-region’ instead with the behavior you proposed.
martin
- mouse-drag-and-drop-region, martin rudalics, 2017/11/14
- Re: mouse-drag-and-drop-region, Alex, 2017/11/15
- Re: mouse-drag-and-drop-region, Eli Zaretskii, 2017/11/15
- Re: mouse-drag-and-drop-region, Alex, 2017/11/15
- Re: mouse-drag-and-drop-region, Eli Zaretskii, 2017/11/16