Paste is broken
This is the result of trying to conflate Pd's internal paste functionality and the "paste Pd code from the clipboard" functionality.
Let's assume that I still have some lines from a Pd patch file in the clipboard, maybe from a previous copy/paste operation some time ago. Now, if I fire up a patch with Purr-Data in order to copy and then paste some objects in the patch, I'm still getting the prompt asking me whether to insert Pd code from the clipboard. This is completely counter-intuitive and not user-friendly. I might well have forgotten about that clipboard contents and now I'm wondering what Purr-Data is trying to do there, when all I want to do is paste those objects that I just copied moments ago.
Worse yet, on Arch using nw.js 0.18.5 I can reproducibly make Purr-Data crash or hang in a similar scenario where I first create a new patch, then open an existing patch, select and copy some objects in the second patch, switch back to the first empty patch, and try to paste there. In the dialog asking me whether I want to insert that Pd code still in the clipboard I press Cancel => Purr-Data crashes with an error message like the following in the terminal:
[6763:6763:1113/193137:ERROR:desktop_window_tree_host_x11.cc(927)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)
Now this is most likely a bug in nw.js, but still.
For these reasons I've disabled the "paste Pd code from the clipboard" stuff in my release branch for now, by uncommenting the corresponding Ctrl+V keybinding for the canvas menu in pd_menus.js, so that the text paste event is not reported to the DOM any more. Everything else seems to work ok with that.
I admit that the "paste Pd code from the clipboard" functionality is cool and very convenient at times. But why not have a dedicated "Paste from clipboard" menu option for it, so that the user actually understands what he's trying to do when he invokes that command? Is it not possible to access the clipboard contents in a direct fashion, or why is that functionality conflated with the Ctrl+V keybinding right now?