After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 651727 - spawn documentation is lacking arguments
spawn documentation is lacking arguments
Status: RESOLVED DUPLICATE of bug 638449
Product: glib
Classification: Platform
Component: docs
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2011-06-02 18:15 UTC by Marc-Andre Lureau
Modified: 2011-06-02 18:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marc-Andre Lureau 2011-06-02 18:15:20 UTC
It seems we lost arguments in the spawn documentation, perhaps it's related to macro handling of gtk-doc.

Compare yourself:

http://developer.gnome.org/glib/stable/glib-Spawning-Processes.html

and

http://developer.gnome.org/glib/2.26/glib-Spawning-Processes.html

#define             g_spawn_async_with_pipes

vs

gboolean            g_spawn_async_with_pipes            (const gchar *working_directory,
                                                         gchar **argv,
                                                         gchar **envp,
                                                         GSpawnFlags flags,
                                                         GSpawnChildSetupFunc child_setup,
                                                         gpointer user_data,
                                                         GPid *child_pid,
                                                         gint *standard_input,
                                                         gint *standard_output,
                                                         gint *standard_error,
                                                         GError **error);
Comment 1 Javier Jardón (IRC: jjardon) 2011-06-02 18:23:33 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 638449 ***