unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: "Paul Magwene, Ph.D." <paul.magwene@duke.edu>,
	43470@debbugs.gnu.org,
	"43470-done@debbugs.gnu.org" <43470-done@debbugs.gnu.org>
Subject: bug#43470: 27.1; Drag and Drop not working properly in 27.1 on OSX
Date: Tue, 22 Sep 2020 13:24:51 +0100	[thread overview]
Message-ID: <20200922122451.GD28875@breton.holly.idiocy.org> (raw)
In-Reply-To: <m1zh5myly8.fsf@yahoo.es>

On Sat, Sep 19, 2020 at 02:45:19PM +0200, Daniel Martín wrote:
> 
> Some applications like Firefox send NSDragOperationEvery when dragging
> URLs or images. That constant means "every possible operation (copy,
> link, move)". When there's more than one operation, we want to
> consider specialized actions like ns-drag-operation-copy before
> generic ones like ns-drag-operation-generic.

Hi Daniel,

I don't think this is correct, we should always choose generic when
it's available as that is the "default" action taken by the
application. The more specialised copy, move, etc., are there for the
sending application (or user via modifiers) to force the receiving
application to do something else.

The big decision is what should Emacs do by default? My opinion is
that when receiving a URL we should insert the link as text rather
than try to open it: Emacs isn't a web browser. Perhaps that's wrong,
I'm not sure what Emacs does on other platforms.

> This change brings back the same drag and drop behavior as in Emacs
> 26.3. (Bug#43470).

This is untrue as the Emacs 26 behaviour was almost entirely arbitrary
and broken. What it does is fix this one particular use-case.
-- 
Alan Third





  reply	other threads:[~2020-09-22 12:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 13:27 bug#43470: 27.1; Drag and Drop not working properly in 27.1 on OSX Paul Magwene, Ph.D.
2020-09-17 17:46 ` Alan Third
2020-09-17 18:12   ` Unknown
2020-09-17 19:46     ` Alan Third
2020-09-18 12:00       ` Unknown
2020-09-18 12:54         ` Alan Third
2020-09-18 18:34           ` Unknown
2020-09-18 19:11             ` Alan Third
2020-09-18 21:27               ` Paul Magwene
2020-09-18 22:15                 ` Alan Third
2020-09-18 23:22                   ` Paul Magwene, Ph.D.
2020-09-19 11:02                     ` Unknown
2020-09-19 12:45                     ` Unknown
2020-09-22 12:24                       ` Alan Third [this message]
2020-09-26 11:39                         ` Unknown
2020-09-27  9:59                           ` Alan Third
2020-09-27 22:22                             ` Unknown
2020-10-03 14:43                               ` Alan Third
2020-09-26 11:39                         ` Unknown
2020-09-19 14:08                     ` Alan Third

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=20200922122451.GD28875@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=43470-done@debbugs.gnu.org \
    --cc=43470@debbugs.gnu.org \
    --cc=mardani29@yahoo.es \
    --cc=paul.magwene@duke.edu \
    /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).