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 621867 - gst-launch: rename new --no-play command line option
gst-launch: rename new --no-play command line option
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal blocker
: 0.10.30
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-17 09:42 UTC by Tim-Philipp Müller
Modified: 2010-07-16 08:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim-Philipp Müller 2010-06-17 09:42:16 UTC 
I think this option should be renamed to something less confusing, that better reflects its fringe feature status. I only noticed this because of the new translated message "Do not install a play handler".

Maybe something like:

 --no-usrsig
 --no-user-signal

or so (or can we just get rid of this functionality?)
Comment 1 Tim-Philipp Müller 2010-06-24 16:27:43 UTC 
commit 1210e4a0061b27b734970c32998a19c2a7c22f80
Author: Tim-Philipp Müller <tim.muller@collabora.co.uk>
Date:   Thu Jun 24 17:22:13 2010 +0100

    gst-launch: rename new --no-play command line option to --no-sigusr-handler
    
    --no-play seems a bit confusing.
    
    Fixes #621867.
Comment 2 Stefan Sauer (gstreamer, gtkdoc dev) 2010-07-16 08:45:02 UTC 
Just for information, I added this to make it usable with ptrace based tools that would like intercepts the signals them self. But I am also wondering if anyone actually use those signals.