FIX: PARSE position capture combined with SET or COPY

The recent extension to allow set-word! usage in SET and COPY rules
introduced a regression: set-word!s (for position capture) in the rule
immediately following a `SET word` or `COPY word` rule cause a match
failure. For example:

    >> parse [x] [set val pos: word!]
    == false  ;; Expected: true

This commit fixes Oldes/Rebol-issues#2130, a regression caused
by 8db79a9.

Corresponding tests have been added to the test suite
(rebolsource/rebol-test@fe8df53).

(cherry picked from commit f540883)

Author: earl

src/core/u-parse.c

@@ -816,11 +816,8 @@ void Print_Parse_Index(REBCNT type, REBVAL *rules, REBSER *series, REBCNT index)
 
 			} else { // It's not a PARSE command, get or set it:
 
-				// word: - if not the target of a COPY or SET operation, this will
-				// default to setting a variable to the series at current index
-				if (IS_SET_WORD(item) &&
-					!(GET_FLAG(flags, PF_SET_OR_COPY) || GET_FLAG(flags, PF_COPY)))
-				{
+				// word: - set a variable to the series at current index
+				if (IS_SET_WORD(item)) {
 					Set_Var_Series(item, parse->type, series, index);
 					continue;
 				}

src/tests/units/parse-test.r3

@@ -95,4 +95,13 @@ Rebol [
 ===end-group===
 
 
+===start-group=== "Other parse issues"
+
+--test-- "issue-2130"
+;@@ https://github.com/Oldes/Rebol-issues/issues/2130
+	--assert parse [x][set val pos: word!]
+	--assert pos = [x]
+
+===end-group===
+
 ~~~end-file~~~