GitLab

For some reason, GUI operations which run for extended periods of time
may cause the engine to crash with a SIGHUP error on Linux. Apparently
this is caused by the watchdog bailing out and taking the engine with
it. This affects the new print operation as well as the existing message
operation in the file menu, possibly also search index generation for
the help browser, and maybe some other operations that still need to be
identified.

The new gui-busy method lets the GUI set an internal flag in the engine
which makes the engine keep the watchdog happy while the GUI does its
thing, using the same mechanism that is already in place to ping the
watchdog when running GUI-less. To these ends, the GUI needs to invoke
"pd gui-busy 1" when starting the time-consuming operation, and "pd
gui-busy 0" when the operation is done.

first draft for opening files from command line or graphical file manager in the current Purr Data instance

first draft of saving the preferences, including the gui preset (still won't write to file for some reason)

from pd-l2ork: 96e2fa5605a2d87ab99c5c2c8df9bca53c23c401

 by Gilberto"
from pd-l2ork: 50719c4c455291be3ac679486f7e4d72706bd9e4

*proxy paste function to incorporate force getscroll to ensure that scroll is being checked after a paste

Protection against closing dirty abstractions
closing and quitting doesn't query if everyone is clean
(but "pd perf" message turns that protection back on for performances)
ctrl-1, etc, automatically place new object under a selected one and
connect to it
return when editing an object (not a message or comment) deactivates text

multiple selection.  Fixed 2-pixel growth problem on Mac.
Made a "version" message so Pd can detect future file formats
if they ever appear.