Re: Drag and drop patch for X, please review.

["Jan D." <jan.h.d@swipnet.se>]

> Earlier I thought you were saying it was too difficult
> to decide based on specific details whether to allow a certain
> drop in a certain buffer.  But now that you've explained that
> every message leads to a LIsp-level event, I can see this is
> not difficult at all.

I probably didn't explain it very well.  I was thinking of text versus
file names.  Dropping a file name on the menu bar, or a read only buffer
is OK, it justs open the file in that window.  But dropping text on the
same place should not insert the text.  So the question was, how can
the code know if somebody has reconfigured the dropping of file names
to actually insert the file name as text instead of opening it?  We can
not know that the drop should be rejected.  But the suggestion made here
was to in that case not reject it, but rather put it in the kill ring
and display a message about it.

>     That is what I am doing now, so if you have several windows in a 
> frame,
>     the one where a file is dropped is used.  This happens anywhere in 
> the
>     buffer, not just the mode line.
>
> That might make sense in most cases.  But Dired buffers should treat
> it differently, and that means it can't be a general Emacs convention.

I'm working on dired so it will handle drop of files as a file manager,
i.e. move, copy or link them to the directory.

	Jan D.