Update flag name

README.md

@@ -248,7 +248,7 @@ SUBCOMMANDS:
 
 The configuration file of Pueue is located in these directories:
 
-- Linux: `$HOME/.config/pueue/pueue.yml`.  
+- Linux: `$HOME/.config/pueue/pueue.yml`.
 - MacOs: `$HOME/Library/Preferences/pueue/pueue.yml`
 - Windows: `%APPDATA%\Local\pueue`
 
@@ -262,9 +262,10 @@ shared:
   pueue_directory: /home/$USER/.local/share/pueue
   use_unix_sockets: false
   unix_sockets_path: /home/$USER/.local/share/pueue/pueue_$USER.socket
+
 client:
   read_local_logs: true
-  print_remove_warnings: false
+  show_confirmation_questions: false
 
 daemon:
   default_parallel_tasks: 1
@@ -276,7 +277,7 @@ daemon:
 
 ### Shared
 
-- `port` The port the daemon listens on and the client connects to in TCP mode.  
+- `port` The port the daemon listens on and the client connects to in TCP mode.
 - `secret` The secret, that's used for authentication
 - `pueue_directory` The location Pueue uses for its intermediate files and logs.
 - `use_unix_sockets` Whether the daemon should listen on a Unix- or a TCP-socket.
@@ -285,12 +286,11 @@ daemon:
 ### Client
 
 - `read_local_logs` If the client runs as the same user (and on the same machine) as the daemon, logs don't have to be sent via the socket but rather read directly.
-- `print_remove_warnings` The client will print warnings that require confirmation for different critical commands.
+- `show_confirmation_questions` The client will print warnings that require confirmation for different critical commands.
 
 ### Daemon
 
-
-- `default_parallel_tasks` Determines how many tasks should be processed concurrently.  
+- `default_parallel_tasks` Determines how many tasks should be processed concurrently.
 - `pause_on_failure` If set to `true`, the daemon stops starting new task as soon as a single task fails. Already running tasks will continue.
 - `callback` The command that will be called after a task finishes. Can be parameterized
 - `groups` This is a list of the groups with their amount of allowed parallel tasks. It's advised to not manipulate this manually, but rather use the `group` subcommand to create and remove groups.

client/client.rs

@@ -258,7 +258,7 @@ impl Client {
                 }))
             }
             SubCommand::Remove { task_ids } => {
-                if self.settings.client.print_remove_warnings {
+                if self.settings.client.show_confirmation_questions {
                     self.handle_user_confirmation("remove", task_ids)?;
                 }
                 Ok(Message::Remove(task_ids.clone()))
@@ -321,7 +321,7 @@ impl Client {
                 all,
                 children,
             } => {
-                if self.settings.client.print_remove_warnings {
+                if self.settings.client.show_confirmation_questions {
                     self.handle_user_confirmation("kill", task_ids)?;
                 }
                 let message = KillMessage {

shared/settings.rs

@@ -24,7 +24,7 @@ pub struct Shared {
 #[derive(Clone, Debug, Deserialize, Serialize)]
 pub struct Client {
     pub read_local_logs: bool,
-    pub print_remove_warnings: bool,
+    pub show_confirmation_questions: bool,
 }
 
 /// All settings which are used by the daemon
@@ -62,7 +62,7 @@ impl Settings {
 
         // Client specific config
         config.set_default("client.read_local_logs", true)?;
-        config.set_default("client.print_remove_warnings", false)?;
+        config.set_default("client.show_confirmation_questions", false)?;
 
         // Daemon specific config
         config.set_default("daemon.default_parallel_tasks", 1)?;