patch 8.2.2141: a user command with try/catch may not catch an expression errorv8.2.2141

Problem:    A user command with try/catch may not catch an expression error.
Solution:   When an expression fails check for following "|". (closes #7469)

1 files changed, 4 insertions, 1 deletions

diff --git a/src/eval.c b/src/eval.c
index 47aaaad23..6ce2ebf68 100644
--- a/src/eval.c
+++ b/src/eval.c
@@ -2158,7 +2158,10 @@ eval0(
 	    semsg(_(e_invexpr2), arg);
 
 	// Some of the expression may not have been consumed.  Do not check for
-	// a next command to avoid more errors.
+	// a next command to avoid more errors, unless "|" is following, which
+	// could only be a command separator.
+	if (eap != NULL && skipwhite(p)[0] == '|' && skipwhite(p)[1] != '|')
+	    eap->nextcmd = check_nextcmd(p);
 	return FAIL;
     }