- * TODO:
- *
- * - Remainder of the context menu:
- *
- * - Event Log (this means we must implement the Event Log; not
- * in pterm)
- *
- * - New Session and Duplicate Session (perhaps in pterm, in fact?!)
- * + Duplicate Session will be fun, since we must work out
- * how to pass the config data through.
- * + In fact this should be easier on Unix, since fork() is
- * available so we need not even exec (this also saves us
- * the trouble of scrabbling around trying to find our own
- * binary). Possible scenario: respond to Duplicate
- * Session by forking. Parent continues as before; child
- * unceremoniously frees all extant resources (backend,
- * terminal, ldisc, frontend etc) and then _longjmps_ (I
- * kid you not) back to a point in pt_main() which causes
- * it to go back round to the point of opening a new
- * terminal window and a new backend.
- * + A tricky bit here is how to free everything without
- * also _destroying_ things - calling GTK to free up
- * existing widgets is liable to send destroy messages to
- * the X server, which won't go down too well with the
- * parent process. exec() is a much cleaner solution to
- * this bit, but requires us to invent some ghastly IPC as
- * we did in Windows PuTTY.
- * + Arrgh! Also, this won't work in pterm since we'll
- * already have dropped privileges by this point, so we
- * can't get another pty. Sigh. Looks like exec has to be
- * the way forward then :-/
- *
- * - Saved Sessions submenu (not in pterm of course)
- *
- * - Change Settings
- * + we must also implement mid-session reconfig in pterm.c.
- * + note this also requires config.c and uxcfg.c to be able
- * to get hold of the application name.
- *
- * - Copy All to Clipboard (for what that's worth)
- */
-
-/*