core: in confirm_spawn, the meaning of 'n' and 's' choices are confusing

Before this patch we had:

 - "no" which gives "failing execution" but the command is actually assumed as
   succeed.

 - "skip" which gives "skipping", but the command is assumed to have failed,
   which ends up with "Failed to start ..." on the console.

Now we have:

 - "fail" which gives "failing execution" and the command is indeed assumed as
   failed.

 - "skip" which gives "skipping execution" and the command is assumed as
   succeed.

1 files changed, 4 insertions, 4 deletions

diff --git a/src/core/execute.c b/src/core/execute.c
index 8b09f71717..10e9dd7cc8 100644
--- a/src/core/execute.c
+++ b/src/core/execute.c
@@ -731,7 +731,7 @@ static int ask_for_confirmation(const char *vc, const char *cmdline) {
                 return CONFIRM_EXECUTE;
         }
 
-        r = ask_char(&c, "yns", "Execute %s? [Yes, No, Skip] ", cmdline);
+        r = ask_char(&c, "yfs", "Execute %s? [Yes, Fail, Skip] ", cmdline);
         if (r < 0) {
                 write_confirm_error_fd(r, STDOUT_FILENO);
                 r = CONFIRM_EXECUTE;
@@ -739,13 +739,13 @@ static int ask_for_confirmation(const char *vc, const char *cmdline) {
         }
 
         switch (c) {
-        case 'n':
+        case 'f':
                 printf("Failing execution.\n");
-                r = CONFIRM_PRETEND_SUCCESS;
+                r = CONFIRM_PRETEND_FAILURE;
                 break;
         case 's':
                 printf("Skipping execution.\n");
-                r = CONFIRM_PRETEND_FAILURE;
+                r = CONFIRM_PRETEND_SUCCESS;
                 break;
         case 'y':
                 r = CONFIRM_EXECUTE;