mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-23 18:21:04 +00:00
5d6635f9b4
Bash 3's completion doesn't split words by characters in COMP_WORDBREAKS. In particular it doesn't split at "=" signs. Now _gst_launch_parse handles both bash 3 and 4 format of COMP_WORDS. Note that "${cur%%=*}" means cur's value with the longest possible match of "=*" deleted from the end; "${cur#*=}" means cur's value with the shortest possible match of "*=" deleted from the beginning. See http://www.gnu.org/software/bash/manual/html_node/Shell-Parameter-Expansion.html Regardless of the version of bash running the unit tests, I can test for both behaviours because the unit test populates COMP_WORDS manually. So this tests the bash 3 behaviour: test_gst_inspect_completion --gst-debug-level=4 and this tests the bash 4 behaviour: test_gst_inspect_completion --gst-debug-level = 4 |
||
---|---|---|
.. | ||
.gitignore | ||
gst-indent | ||
gst-inspect.1.in | ||
gst-inspect.c | ||
gst-launch.1.in | ||
gst-launch.c | ||
gst-plot-timeline.py | ||
gst-typefind.1.in | ||
gst-typefind.c | ||
gstreamer-completion | ||
Makefile.am | ||
tools.h |