From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, storm@cua.dk,
miles@gnu.org
Subject: Re: Drag and drop patch for X, please review.
Date: Sat, 24 Jan 2004 16:39:58 -0500 [thread overview]
Message-ID: <E1AkVVW-0000AF-4G@fencepost.gnu.org> (raw)
In-Reply-To: <6FAAFF66-4DDF-11D8-B739-00039363E640@swipnet.se> (jan.h.d@swipnet.se)
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?
I don't see why it is difficult to give the user a way to specify the
answers.
> 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.
Thanks. The point I am making now is that we want to teach people
something else--such as dropping on a mode line--as the way
to visit a file. That would work regardless of what kind of buffer
is currently displayed in the window.
next prev parent reply other threads:[~2004-01-24 21:39 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.
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 [this message]
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=E1AkVVW-0000AF-4G@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=storm@cua.dk \
/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).