From: add-uos-ffmpeg via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: add-uos-ffmpeg <code@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] WIP: fftools/opt_common: add separator line to show_filters output (PR #20547) Date: Thu, 18 Sep 2025 11:17:04 -0000 Message-ID: <175819422498.25.14942426735774396469@463a07221176> (raw) PR #20547 opened by add-uos-ffmpeg URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20547 Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20547.patch Add a separator line to show_filters() function output to maintain consistent formatting with other show functions like show_codecs, show_formats_devices, etc. This provides uniform formatting across all command-line output functions for better readability and parsing by external tools. >From d16eae0c323e61131151c289a28790af365f7c09 Mon Sep 17 00:00:00 2001 From: zhanghongyuan <zhanghongyuan@uniontech.com> Date: Tue, 2 Sep 2025 15:03:39 +0800 Subject: [PATCH] fftools/opt_common: add separator line to show_filters output Add a separator line to show_filters() function output to maintain consistent formatting with other show functions like show_codecs, show_formats_devices, etc. This provides uniform formatting across all command-line output functions for better readability and parsing by external tools. --- fftools/opt_common.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fftools/opt_common.c b/fftools/opt_common.c index 5dcb14e261..e217456be7 100644 --- a/fftools/opt_common.c +++ b/fftools/opt_common.c @@ -809,7 +809,8 @@ int show_filters(void *optctx, const char *opt, const char *arg) " A = Audio input/output\n" " V = Video input/output\n" " N = Dynamic number and/or type of input/output\n" - " | = Source or sink filter\n"); + " | = Source or sink filter\n" + " ------\n"); while ((filter = av_filter_iterate(&opaque))) { descr_cur = descr; for (i = 0; i < 2; i++) { -- 2.49.1 _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-09-18 11:17 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=175819422498.25.14942426735774396469@463a07221176 \ --to=ffmpeg-devel@ffmpeg.org \ --cc=code@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git