1. 14 Jan, 2021 1 commit
  2. 04 Jan, 2021 1 commit
  3. 02 Jan, 2021 1 commit
  4. 01 Jan, 2021 1 commit
  5. 30 Dec, 2020 2 commits
  6. 29 Dec, 2020 1 commit
  7. 28 Dec, 2020 1 commit
  8. 27 Dec, 2020 2 commits
  9. 22 Dec, 2020 2 commits
  10. 19 Dec, 2020 1 commit
  11. 13 Dec, 2020 1 commit
    • Evangelos Foutras's avatar
      Stop using G_SPAWN_CHILD_INHERITS_STDIN spawn flag · 7a77c485
      Evangelos Foutras authored
      When this flag gets passed to vte_terminal_spawn_async(), vte 0.62 warns
      about it being part of the flag set returned by forbidden_spawn_flags().
      
      Looking at the minimum required version, vte 0.38, vte itself used to
      automatically add G_SPAWN_CHILD_INHERITS_STDIN to the spawn flags. It
      stopped doing that in the 0.47.90 release and the commit message was:
      
        (GNOME/vte) commit b517d20379c7a665e897f925ca3ecb7b778364f2
      
        pty: Do not pass G_SPAWN_CHILD_INHERITS_STDIN
      
        This makes no sense at all, since we redirect stdin to the PTY anyway.
        Fixes a FIXME!
      
      So, considering that:
      
        - vte used to add this flag automatically in past
        - vte dropped the flag as unnecessary in v0.47.90
        - vte 0.62 is warning about it and is ignoring it
        - the warning might be upgraded to a g_return_if_fail() in the future
      
      It seems reasonable and safe to stop using the flag ourselves. :)
      
      Fixes: #86
      7a77c485
  12. 11 Dec, 2020 1 commit
  13. 07 Dec, 2020 1 commit
  14. 04 Dec, 2020 1 commit
  15. 20 Nov, 2020 1 commit
  16. 18 Nov, 2020 1 commit
  17. 16 Nov, 2020 1 commit
  18. 09 Nov, 2020 1 commit
  19. 08 Nov, 2020 1 commit
  20. 01 Nov, 2020 1 commit
  21. 31 Oct, 2020 1 commit
  22. 29 Oct, 2020 2 commits
  23. 27 Oct, 2020 1 commit
  24. 26 Oct, 2020 1 commit
  25. 24 Oct, 2020 1 commit
  26. 23 Oct, 2020 1 commit
  27. 22 Oct, 2020 3 commits
  28. 21 Oct, 2020 6 commits
  29. 20 Oct, 2020 1 commit