From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca,
miles@gnu.org
Subject: Re: Drag and drop patch for X, please review.
Date: Thu, 22 Jan 2004 10:46:03 +0100 [thread overview]
Message-ID: <CAFB0240-4CBF-11D8-B12B-00039363E640@swipnet.se> (raw)
In-Reply-To: <m3oeswguah.fsf@kfs-l.imdomain.dk>
>>> 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.
next prev parent reply other threads:[~2004-01-22 9:46 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.
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. [this message]
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=CAFB0240-4CBF-11D8-B12B-00039363E640@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).