unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: Miles Bader <miles@gnu.org>, emacs-devel@gnu.org
Subject: Re: Drag and drop patch for X, please review.
Date: Mon, 19 Jan 2004 21:47:18 +0100	[thread overview]
Message-ID: <ABA97F46-4AC0-11D8-BCBC-00039363E640@swipnet.se> (raw)
In-Reply-To: <jwvsmibls0q.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>

>> frame, it is hard to select the one the user intended.  Also, if the
>> buffer is read only, we don't want to accept a drop there.  So 
>> currently
>
> I'd argue that we want to accept the drop (and then signal an error).
> Just like C-y is accepted (i.e. the yank function is invoked) but then
> signals an error.
>
> Now that I think about it, rather than an alist, we might just want to 
> make
> the drop into an event that we look up in the keymaps.  If the drop is 
> in
> the tool-bar or the menu-bar, the event generated should be different 
> so
> that we can bind it to a different command (just like [mouse-1] turns 
> into
> [mode-line mouse-1] when clicking on the mode-line).

This is not compatible with the current drop code for W32.  Also, I 
don't
think it is worth doing, it is too complex for very little user benefit.
Better then to accept the drop and put it in the kill ring if we can't
insert it into a buffer.

	Jan D.

  reply	other threads:[~2004-01-19 20:47 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17 16:35 Drag and drop patch for X, please review Jan D.
2004-01-17 20:20 ` David Kastrup
2004-01-18 20:22   ` Jan D.
2004-01-18 21:50     ` Kim F. Storm
2004-01-18 21:09       ` Jan D.
2004-01-18  0:40 ` Miles Bader
2004-01-18 20:44   ` Jan D.
2004-01-18 21:34     ` Kai Grossjohann
2004-01-18 21:55       ` Jan D.
2004-01-18 23:08         ` Miles Bader
2004-01-19 20:12           ` Richard Stallman
2004-01-19 20:43           ` Jan D.
2004-01-20  2:34             ` Miles Bader
2004-01-19 20:49           ` Jan D.
2004-01-18 22:10     ` Kim F. Storm
2004-01-18 21:14       ` Jan D.
2004-01-19 18:24     ` Stefan Monnier
2004-01-19 20:47       ` Jan D. [this message]
2004-01-19 23:35         ` Jason Rumney
2004-01-19 23:50           ` Jan D.
2004-01-20 15:52         ` Stefan Monnier
2004-01-20 16:05           ` Jan D.
2004-01-20 18:41             ` Stefan Monnier
2004-01-20 20:50               ` Jan D.
2004-01-20 21:12                 ` Stefan Monnier
2004-01-20 21:27                   ` Jan D.
2004-01-20 22:09                     ` Stefan Monnier
2004-01-20 22:28                       ` Jan D.
2004-01-20 23:38                         ` Stefan Monnier
2004-01-21 21:08                 ` Richard Stallman
2004-01-21 22:30                   ` Jan D.
2004-01-22 10:19                     ` Kim F. Storm
2004-01-22  9:46                       ` Jan D.
2004-01-22 11:32                         ` Kim F. Storm
2004-01-23 18:25                         ` Richard Stallman
2004-01-23 20:05                           ` Jan D.
2004-01-24 21:39                             ` Richard Stallman
2004-01-18 19:14 ` Richard Stallman
2004-01-18 21:02   ` Jan D.
2004-01-19 20:12     ` Richard Stallman
2004-01-19 21:14       ` Jan D.
2004-01-20 15:31         ` Richard Stallman
2004-01-20 15:49           ` Jan D.
2004-01-21 21:09             ` Richard Stallman
2004-01-21 22:22               ` Jan D.
2004-01-22 19:00                 ` Richard Stallman
2004-01-22 19:27                   ` Jan D.
2004-01-20 16:02         ` Stefan Monnier
2004-01-20 16:24           ` Jan D.
2004-01-20 18:43             ` Stefan Monnier
2004-01-20 20:33               ` Jan D.
2004-01-20 20:43                 ` Stefan Monnier
2004-01-21 21:08               ` Richard Stallman
2004-01-21 21:14                 ` Stefan Monnier
2004-01-21 22:02                   ` Jan D.
2004-01-18 19:16 ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ABA97F46-4AC0-11D8-BCBC-00039363E640@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).