[Question] Would it be more user-friendly to not panic when binwalk is run with no arguments?

[Adamkadaban]

This is very minor, but when I first ran v3 I saw the first and last line and automatically assumed binwalk was broken without reading the panic message.

Almost every other tool I use prints the help menu by default when run with no arguments.

I think just exiting rather than panicking would also be more consistent with what binwalk currently prints when invalid arguments are passed

Thoughts on switching panic! for one of the following?

Error and exit here

diff --git a/src/main.rs b/src/main.rs
index ed46ef5..50e22e7 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -68,7 +68,8 @@ fn main() {
 
     // If --list was not specified, a target file must be provided
     if cliargs.file_name.is_none() {
-        panic!("No target file name specified! Try --help.");
+        eprintln!("No target file name specified! Try --help.");
+        process::exit(1);
     }
 
     let mut json_logger = json::JsonLogger::new(cliargs.log);

Print help menu and exit here

diff --git a/src/cliparser.rs b/src/cliparser.rs
index ff7e89e..8a0605a 100644
--- a/src/cliparser.rs
+++ b/src/cliparser.rs
@@ -1,4 +1,4 @@
-use clap::Parser;
+use clap::{CommandFactory, Parser};
 
 #[derive(Debug, Parser)]
 #[command(author, version, about, long_about = None)]
@@ -68,5 +68,14 @@ pub struct CliArgs {
 }
 
 pub fn parse() -> CliArgs {
-    CliArgs::parse()
+    let args = CliArgs::parse();
+
+    if std::env::args().len() == 1 {
+        CliArgs::command()
+            .print_help()
+            .expect("Failed to print help");
+        std::process::exit(0);
+    }
+
+    args
 }

If one of these is something you think is reasonable, I can formalize it in a PR