GNOME Bugzilla – Bug 649004
Vte: Vte.Terminal.fork_command_full some arguments can be nullable
Last modified: 2013-04-16 08:07:31 UTC
Created attachment 186924 [details] [review] The patch to resolve it Vte in version >= 0.26 had the function Vte.Terminal.fork_command_full. But in the vte vapi file, this function had some arguments non-nullable and some other arguments nullable. That should be the opposite. (see: http://developer.gnome.org/vte/0.26/VteTerminal.html#vte-terminal-fork-command-full) In the api documentation we can see that argv argument can't be nullable, child_setup can be nullable and child_pid too. For the child_pid case, the argument is not a variable but a pointer nullable.
commit c677d391f598f88354467ceb70bc857d28fd04d2 Author: Luca Bruno <lucabru@src.gnome.org> Date: Sat Apr 30 17:38:10 2011 +0200 vte: Fix Terminal.fork_command_full binding Based on patch by Jacques-Pascal Deplaix. Fixes bug 649004. This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
I'm still having difficulties getting child_pid to be accessable. All the other named parameters that I tried appear to work, accept it. https://bugzilla.gnome.org/show_bug.cgi?id=688699 I am using libvte-2.90 via Python 3 over the GObject introspection interface.
I realized what I am doing wrong. The child_pid is specified as an out parameter via introspection, so the return value of fork_command_full() is a tuple containing the success code and the child_pid in that order.