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 672649 - vte_terminal_fork_command_full unusable
vte_terminal_fork_command_full unusable
Status: RESOLVED OBSOLETE
Product: vte
Classification: Core
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: VTE Maintainers
VTE Maintainers
[fixed-next]
Depends on:
Blocks: vte1.0
 
 
Reported: 2012-03-22 20:25 UTC by Christian Persch
Modified: 2020-04-27 20:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Persch 2012-03-22 20:25:42 UTC
vte_terminal_fork_command_full() is unusable with a custom child setup function, since there's no way to pass the VtePty to it, but that's required since calling vte_pty_child_setup() is mandatory in custom child setup functions.

For 1.0 we can just break API, but until then another solution is needed. Perhaps use one of the free bits in GSpawnFlags for a vte flag that makes __vte_pty_spawn() put the VtePty* into the passed child_setup_data at offset 0 ?
Comment 1 Christian Persch 2012-03-27 12:13:01 UTC
Fixed on vte-0-32 and vte-next by making vte_pty_child_setup() just call the provided extra child setup function.

Leaving open however as reminder to try and improve this API.