1. 06 Feb, 2014 1 commit
  2. 31 Jan, 2014 1 commit
  3. 17 Oct, 2013 1 commit
  4. 01 Jul, 2013 2 commits
  5. 21 May, 2013 1 commit
    • Dan Winship's avatar
      Use 'dumb quotes' rather than `really dumb quotes' · 4b94c083
      Dan Winship authored
      Back in the far-off twentieth century, it was normal on unix
      workstations for U+0060 GRAVE ACCENT to be drawn as "‛" and for U+0027
      APOSTROPHE to be drawn as "’". This led to the convention of using
      them as poor-man's ‛smart quotes’ in ASCII-only text.
      However, "'" is now universally drawn as a vertical line, and "`" at a
      45-degree angle, making them an `odd couple' when used together.
      Unfortunately, there are lots of very old strings in glib, and also
      lots of new strings in which people have kept up the old tradition,
      perhaps entirely unaware that it used to not look stupid.
      Fix this by just using 'dumb quotes' everywhere.
  6. 23 Apr, 2013 1 commit
  7. 29 Jan, 2013 1 commit
    • Colin Walters's avatar
      Add g_close(), use it · f398bec5
      Colin Walters authored
      There are two benefits to this:
      1) We can centralize any operating system specific knowledge of
         close-vs-EINTR handling.  For example, while on Linux we should never
         retry, if someone cared enough later about HP-UX, they could come by
         and change this one spot.
      2) For places that do care about the return value and want to provide
         the caller with a GError, this function makes it convenient to do so.
      Note that gspawn.c had an incorrect EINTR loop-retry around close().
  8. 15 Nov, 2012 1 commit
  9. 14 Nov, 2012 1 commit
  10. 02 Nov, 2012 1 commit
    • Colin Walters's avatar
      Merge waitpid() from g_spawn_sync into gmain() · ce002293
      Colin Walters authored
      This is preparatory work for a future commit which will add a
      "catchall" waitpid API.  If we don't synchronize here with the worker
      thread, race conditions are possible.
      This also ensures we have an error message if someone adds a child
      watch for a nonexistent pid, etc.  Previously, we'd simply keep
      calling waitpid() getting ECHILD, and ignoring it until the source was
      removed. Now, we g_warning() and fire the source.
      Thirdly, this ensures that the waitpid() call in gmain handles EINTR,
      like the g_spawn_sync() one did.
  11. 29 Oct, 2012 1 commit
    • Paul Eggert's avatar
      gmain: Document constraints on waitpid · 00f4c12b
      Paul Eggert authored
      Applications that use glib should not invoke waitpid with a first
      argument that is nonpositive, because when such a waitpid is run in
      one thread and glib waits for a subprocess in another, there is a race
      condition, and the former waitpid can reap a process that was intended
      for the latter.  Mention this in the documentation for
      g_child_watch_source_new, and in the diagnostic generated by
      g_spawn_sync when its waitpid fails with errno equal to ECHILD.
      Signed-off-by: Colin Walters's avatarColin Walters <walters@verbum.org>
  12. 28 Aug, 2012 3 commits
  13. 13 Jul, 2012 1 commit
  14. 10 Jul, 2012 1 commit
    • Colin Walters's avatar
      Add g_spawn_check_exit_status() · f7abd3ce
      Colin Walters authored
      Many (if not "almost all") programs that spawn other programs via
      g_spawn_sync() or the like simply want to check whether or not the
      child exited successfully, but doing so requires use of
      platform-specific functionality and there's actually a fair amount of
      boilerplate involved.
      This new API will help drain a *lot* of mostly duplicated code in
      GNOME, from gnome-session to gdm.  And we can see that some bits even
      inside GLib were doing it wrong; for example checking the exit status
      on Unix, but ignoring it on Windows.
  15. 22 Jun, 2012 1 commit
  16. 22 May, 2012 1 commit
    • Christian Persch's avatar
      gspawn: Add GSpawnFlag to use the PATH from envp · 481191f1
      Christian Persch authored
      Add a G_SPAWN_SEARCH_PATH_FROM_ENVP flag to GSpawnFlags so that
      g_spawn_async() etc use the PATH variable from the passed-in child
      environment to search for the executable.
      If both this flag and the G_SPAWN_SEARCH_PATH flag are set, the
      child environment is searched first and only falls back to the
      PATH from the process environment if it is unset.
      Bug #676398.
  17. 16 Mar, 2012 1 commit
  18. 03 Mar, 2012 1 commit
  19. 14 Dec, 2011 1 commit
  20. 16 Oct, 2011 2 commits
  21. 05 Sep, 2011 1 commit
  22. 06 Jul, 2011 1 commit
  23. 15 Jun, 2011 1 commit
  24. 14 Jun, 2011 2 commits
  25. 10 Jun, 2011 1 commit
  26. 07 Jun, 2011 1 commit
  27. 06 Sep, 2010 1 commit
  28. 05 Sep, 2010 1 commit
  29. 07 Jul, 2010 1 commit
  30. 22 Aug, 2009 1 commit
  31. 20 May, 2009 1 commit
  32. 31 Dec, 2008 1 commit
  33. 25 Sep, 2008 1 commit
    • Tor Lillqvist's avatar
      Just ignore the child_setup function, never call it. The is no situation · 0ed8b94b
      Tor Lillqvist authored
      2008-09-25  Tor Lillqvist  <tml@novell.com>
      	* glib/gspawn-win32.c (do_spawn_with_pipes) (do_spawn_directly):
      	Just ignore the child_setup function, never call it. The is no
      	situation in which it could be useful on Windows. Do print a
      	warning, like before.
      	* glib/gspawn.c (g_spawn_async_with_pipes): Corresponding change
      	in documentation.
      svn path=/trunk/; revision=7540
  34. 11 Jun, 2008 1 commit
  35. 25 May, 2008 1 commit