mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-03 21:23:48 +00:00
[CLI] Improve user feedback when CCExtractor is run without an input file #886
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Drishtipixiee on GitHub (Jan 2, 2026).
Description:
While testing CCExtractor from the terminal, I noticed that running the tool
without providing an input media file may be confusing for new users.
Steps to reproduce:
Expected behavior:
CCExtractor could display a clear message indicating that an input media file
is required, along with a brief usage hint.
Current behavior:
The current output does not clearly explain that an input file is missing.
Why this matters:
Clear CLI feedback improves usability for new users and helps avoid confusion
when CCExtractor is used in scripts or terminal-based workflows.
I have built CCExtractor locally and would be happy to work on a fix
if this improvement is approved.
@Drishtipixiee commented on GitHub (Jan 2, 2026):
just checking in — I’m happy to work on this if it looks good to maintainers.
thanks!
@Akki2005 commented on GitHub (Jan 3, 2026):
Hi, thanks for opening this issue.
I tested this on a clean setup (WSL/Linux), starting from a fresh clone of the repository. When running ./ccextractor without providing an input media file, the output does not clearly indicate that an input file is required, which could be confusing for new users.
While setting this up, I also attempted a standard Linux build using the provided autotools flow (linux/autogen.sh → configure → make). On a clean tree, the build currently fails at the linking stage due to an unresolved Rust symbol (ccxr_update_logger_target), so I couldn’t fully test runtime behavior beyond this point.
That said, the UX concern raised here still seems valid: it would be helpful if the CLI explicitly reported a missing input file and showed a brief usage hint.
I’d be happy to work on a fix or investigate further if this improvement is considered useful.
@cfsmp3 commented on GitHub (Jan 3, 2026):
If you are seeing a build problem and have a user reported UI problem you haven't seen yourself, which one do you think you should be working on :-)
@Drishtipixiee commented on GitHub (Jan 3, 2026):
Got it — that makes sense 🙂I agree the build issue is higher priority. i took some time to look into the unresolved Rust symbol (ccxr_update_logger_target) and it appears to be a deeper build-level issue than I can reasonably take on right now. Given that, I’ll pause work on this for the moment and focus on other contributions. happy to revisit the CLI UX improvement later if this becomes actionable.
Thanks!
@Akki2005 commented on GitHub (Jan 3, 2026):
That’s a fair point — thanks for clarifying.
My intent was mainly to confirm the CLI UX concern raised in the issue and offer help, not to redirect focus away from higher-priority build problems.
@Anushka-google commented on GitHub (Jan 18, 2026):
Hi maintainers,
I’ve gone through the issue and checked the current CLI behavior when CCExtractor is run without an input file.
I understand that in this case the tool should provide clearer, more user-friendly feedback instead of the existing response.
I’d like to work on this by tracing the CLI argument parsing in the main entry point, adding a guard for missing input files, and improving the error message and usage hint to better guide users.
Please let me know if I can proceed and assign this issue to me.
Thank you for your time.
@cfsmp3 commented on GitHub (Jan 19, 2026):
I'm closing this, I don't think this is an actual issue. We can't have an issue for something this trivial. If someone wants to make the change, go ahead.