From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Jan D." Newsgroups: gmane.emacs.devel Subject: Re: Drag and drop patch for X, please review. Date: Wed, 21 Jan 2004 23:30:34 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <6DDE2AC7-4C61-11D8-89BA-00039363E640@swipnet.se> References: <200401171729.i0HHT1wq016912@stubby.bodenonline.com> <20040118004009.GA24635@fencepost> <2C5AAB61-49F7-11D8-A763-00039363E640@swipnet.se> <74293710-4B62-11D8-89AF-00039363E640@swipnet.se> <39277C06-4B8A-11D8-AF87-00039363E640@swipnet.se> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (Apple Message framework v609) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1074725788 28319 80.91.224.253 (21 Jan 2004 22:56:28 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 21 Jan 2004 22:56:28 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, miles@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Jan 21 23:56:15 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AjRGg-0002GK-00 for ; Wed, 21 Jan 2004 23:56:14 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AjRGg-0001Hp-00 for ; Wed, 21 Jan 2004 23:56:14 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AjRE1-0005Ul-UQ for emacs-devel@quimby.gnus.org; Wed, 21 Jan 2004 17:53:29 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AjRCE-00053e-AF for emacs-devel@gnu.org; Wed, 21 Jan 2004 17:51:38 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AjR7F-0003Ob-4d for emacs-devel@gnu.org; Wed, 21 Jan 2004 17:47:01 -0500 Original-Received: from [213.115.192.53] (helo=mail2.norrnet.net) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AjQt3-00007s-63; Wed, 21 Jan 2004 17:31:49 -0500 Original-Received: from stubby.bodenonline.com (stubby.bodenonline.com [193.201.16.94]) by mail2.norrnet.net (BorderWare MXtreme Mail Firewall) with ESMTP id 1078155E68; Wed, 21 Jan 2004 23:31:42 +0100 (CET) Original-Received: from accessno42.bodenonline.com (accessno42.bodenonline.com [193.201.16.44]) by stubby.bodenonline.com (8.12.1/8.12.1) with ESMTP id i0LNNh7L030705; Thu, 22 Jan 2004 00:23:44 +0100 In-Reply-To: Original-To: rms@gnu.org X-Mailer: Apple Mail (2.609) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:19420 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19420 > > I think it is better not to try to say yes and no in different Emacs > buffers. We should treat all of the buffer text areas in a uniform way > as regards accepting drops there. Okay, then we can put the data in the kill ring if it can't be inserted. > However, the menu bars could be treated differently, since the C code > can tell whether the pointer is in a menu bar. Likewise, maybe Emacs > could always reject drops in scroll bars, or in the echo area when the > minibuffer is inactive (or maybe always in the echo area). The C code > can tell if a window is a minibuffer window and whether it is active. > > Mode lines also would have to be treated uniformly, I guess. > Is there a useful meaning for a drop in the mode line? Well, if a drop of a file opens the file, it should do it for the mode line also I think. > Different buffers can still handle the same kind of drop in different > ways, based on local key bindings. There's no need to look thus up > except at the end, in response to the event. The current drag and drop event from C to Lisp is not intended to be anything but internal, i.e. to be able to implement the protocol in lisp. I guess I could create an additional event for the final drop, but information must be extraced before the final event (see other mails). > > If we want dropping a file into the menu bar to open the file, then I > suggest it open the file using find-file-other-window. While no > method is always best, that's the way users most often prefer. That is easy to do. Jan D.