Remove stderr comment output for generate-completion subcommand

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## [Unreleased]
+
+### Changed
+
+- Remove stderr comment output for `tinty generate-completion`
+
 ## [0.14.0] - 2024-05-07
 
 ### Added

USAGE.md

@@ -21,6 +21,18 @@ subcommand, source the generated file in your shell startup file (`*rc`)
 and completions will exist for `tinty`. Have a look at the [README CLI
 section] for more information about the command usage.
 
+```sh
+tinty generate-completion zsh > path/to/tinty-zsh-completion.sh
+```
+
+In your startup file (`*rc`) add the following:
+
+```sh
+source path/to/tinty-zsh-completion.sh
+```
+
+### Completions in the repo
+
 A shell completion generation via `tinty` doesn't include any dynamic
 values, meaning scheme names (such as `base16-ocean`) won't be completed
 typing `tinty apply base`. We've created modified completion script

src/main.rs

@@ -88,7 +88,7 @@ fn main() -> Result<()> {
         Some(("generate-completion", sub_matches)) => {
             if let Some(generator) = sub_matches.get_one::<Shell>("shell_name") {
                 let mut cmd = build_cli();
-                eprintln!("Generating completion file for {generator}...");
+
                 print_completions(*generator, &mut cmd);
                 return Ok(());
             };

tests/cli_generatecompletion_subcommand_tests.rs

@@ -15,17 +15,7 @@ fn generate_shell_completion_test(shell_name: &str) -> Result<String> {
     // ---
     // Act
     // ---
-    let (stdout, stderr) = utils::run_command(command_vec).unwrap();
-
-    // Ok((stdout, stderr, cleanup))
-
-    // ------
-    // Assert
-    // ------
-    assert!(
-        stderr.contains(format!("Generating completion file for {shell_name}...").as_str()),
-        "stderr does not contain the expected output"
-    );
+    let (stdout, _) = utils::run_command(command_vec).unwrap();
 
     cleanup()?;
     Ok(stdout)