From: Glenn Morris <rgm@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 10050@debbugs.gnu.org, Adam Winiecki <adam.winiecki@gmail.com>
Subject: bug#10050: 24.0.90; image files display image data only after drag and drop
Date: Wed, 22 Feb 2012 03:08:53 -0500 [thread overview]
Message-ID: <8yvcmzmgru.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <6424E76B-907E-4C5D-B959-5BA0ECA4C64D@swipnet.se> ("Jan Djärv"'s message of "Sat, 10 Dec 2011 17:27:58 +0100")
Jan Djärv wrote:
> The big problem is that dragging a file to Emacs on NS inserts the
> contents of that file to the current buffer instead of opening it as
> people normally expect, and indeed is what all other Emacs versions
> does. It is like that in Emacs 23 also, so this is not a regression.
> But as we are in a feature freeze this will have to wait, even if the
> behaviour is stupid. If Emacs would open dragged files in a new
> buffer, images would be shown as images.
Is it just a question of doing what it says in the manual, or is more
needed?
The default behavior when a user drags files from another application
into an Emacs frame is to insert the contents of all the dragged files
into the current buffer. To remap the `ns-drag-file' event to open the
dragged files in the current frame use the following line:
(define-key global-map [ns-drag-file] 'ns-find-file)
Maybe that change is sensible and safe enough for 24.1.
(I can't even test it so I wouldn't know.)
next prev parent reply other threads:[~2012-02-22 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 19:37 bug#10050: 24.0.90; image files display image data only after drag and drop Adam Winiecki
2011-12-10 16:27 ` Jan Djärv
2012-02-22 8:08 ` Glenn Morris [this message]
2012-02-22 11:05 ` Jan Djärv
2012-02-22 17:23 ` Glenn Morris
2012-02-25 3:59 ` Chong Yidong
2012-02-25 10:06 ` Jan Djärv
2012-02-26 9:17 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8yvcmzmgru.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=10050@debbugs.gnu.org \
--cc=adam.winiecki@gmail.com \
--cc=jan.h.d@swipnet.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.