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: Thu, 22 Jan 2004 10:46:03 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: 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> <6DDE2AC7-4C61-11D8-89BA-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 1074765102 29332 80.91.224.253 (22 Jan 2004 09:51:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 22 Jan 2004 09:51:42 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca, miles@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Jan 22 10:51:31 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 1AjbUp-0005Qz-00 for ; Thu, 22 Jan 2004 10:51:31 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AjbUo-0005mz-00 for ; Thu, 22 Jan 2004 10:51:30 +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 1AjbSc-0004E0-0h for emacs-devel@quimby.gnus.org; Thu, 22 Jan 2004 04:49:14 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AjbQp-0003bo-Vr for emacs-devel@gnu.org; Thu, 22 Jan 2004 04:47:23 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AjbQD-0002jF-Mw for emacs-devel@gnu.org; Thu, 22 Jan 2004 04:47:19 -0500 Original-Received: from [213.115.192.53] (helo=mail2.norrnet.net) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AjbQB-0002ca-ND; Thu, 22 Jan 2004 04:46:43 -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 72EB73EA98; Thu, 22 Jan 2004 10:46:48 +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 i0MAcg7L007125; Thu, 22 Jan 2004 11:38:53 +0100 In-Reply-To: Original-To: storm@cua.dk (Kim F. Storm) 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:19423 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19423 >>> 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). > > IMO, dropping it in the echo area/mini buffer should mean to copy the > file-name/whatever to the kill-ring unconditionally. Hmm, I think it is likely that someone might want to drop say a file name (i.e. mark a file name in some other application and drag it to Emacs) to the mini buffer, and really have the text inserted there. I am talking about dragging text here, not a uri-list, which currently opens the file instead (for example, dragging from a file manager). I think this operation is the same as doing copy/past with the mouse from another application to Emacs mini buffer. Wouldn't it be strange if drag-drop and copy-paste behaved differently for the mini buffer? >>> >>> 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. > > But contrary to dropping it on the menu-bar (which does > find-file-other-window), I think that dropping it on the mode line of > a window should open the file in that window. 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. Jan D.