From: Alan Third <alan@idiocy.org>
To: Nick Helm <nick@tenpoint.co.nz>
Cc: 30929@debbugs.gnu.org
Subject: bug#30929: 26.0.91; Text drag and drop does not work
Date: Fri, 13 Apr 2018 19:33:34 +0100 [thread overview]
Message-ID: <20180413183334.GA39515@breton.holly.idiocy.org> (raw)
In-Reply-To: <m24lkhasyu.fsf@tenpoint.co.nz>
On Thu, Apr 12, 2018 at 05:34:17PM +1200, Nick Helm wrote:
> On Wed, 11 Apr 2018 at 07:38:24 +1200, Alan Third wrote:
>
> > On Mon, Apr 09, 2018 at 01:51:58PM +1200, Nick Helm wrote:
>
> > This is probably a better idea, we pass the string, the type (from the
> > PB) and the mask to lisp, and then let ns-drag-n-drop sort it out.
> > Like you say, if an expert wants to do something different they can
> > then write their own function.
> >
> > So in C we just construct something like:
> >
> > '(file
> > (ns-drag-operation-copy
> > ns-drag-operation-link)
> > "filename")
> >
> > Are you wanting to give this a go? I’m happy to work on it if not.
>
> Ok, I see what you mean. Yep, I can have a go at it.
I look forward to it.
BTW, there’s some code in the drag and drop stuff that sets
ns_input_file. You don’t need that, it’s not used for DnD and, in
fact, causes problems with other ways of opening files.
(More info in commit 292c09ff6db4bba1655bbb3160e859fef59ab34b and
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29121, which I now see
was raised by you. :) )
--
Alan Third
next prev parent reply other threads:[~2018-04-13 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 12:28 bug#30929: 26.0.91; Text drag and drop does not work Nick Helm
2018-03-25 11:57 ` Alan Third
2018-03-28 9:20 ` Nick Helm
2018-04-07 15:01 ` Alan Third
2018-04-09 1:51 ` Nick Helm
2018-04-10 19:38 ` Alan Third
2018-04-12 5:34 ` Nick Helm
2018-04-13 18:33 ` Alan Third [this message]
2018-04-24 12:42 ` Nick Helm
2018-04-24 18:19 ` Alan Third
2018-04-25 23:16 ` Nick Helm
2018-04-26 20:44 ` Alan Third
2018-04-28 9:57 ` Nick Helm
2019-01-05 10:27 ` Alan Third
2019-01-05 13:05 ` Nick Helm
2019-01-05 16:20 ` Alan Third
2019-01-07 10:38 ` Nick Helm
2019-01-10 19:23 ` 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=20180413183334.GA39515@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=30929@debbugs.gnu.org \
--cc=nick@tenpoint.co.nz \
/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).