bug#18090: 24.4.50; `delete-selection-helper' logic changed for non-mouse region?

[Drew Adams <drew.adams@oracle.com>]

> > As you say, mouse-yank commands are not supported by
> > `delete-selection-mode' - they do not have a `yank'
> > `delete-selection-mode' property value.

(I meant `delete-selection' property value.)

> Shouldn't mouse yanking be supported by `delete-selection-mode',
> what do you think?

Dunno. Please file a bug report, if you think so. Or
feel free to bring that into this report, if you like.

What do you want it to do? Does it do what you want if you
(put 'mouse-yank-primary 'delete-selection 'yank)?
If not, what code change do you think is needed?

> I agree that code that calls (delete-active-region) under the
> condition (eq type 'yank) is essential to handle `yank'.
> But I think that (current-kill 1) is not essential
> unless it renders yank useless in some cases (yet unknown).

Maybe you're right; dunno.

Do you want to remove that code? Without it, does
`deletion-selection-mode' do what you want for both
t and nil values of `mouse-drag-copy-region'?

At this point it's not clear to me what behavior is  bugged,
if any. I'd like to hear what changes, if any, you propose,
both for the code and the desired behavior (for both t
and nil values of `mouse-drag-copy-region').