Compare commits
No commits in common. "6d21c2a1de9cb88479a0e67df492da3f3bbdb054" and "45e2c0249263ca33f462f12895f1050861231c4c" have entirely different histories.
6d21c2a1de
...
45e2c02492
|
|
@ -295,10 +295,8 @@ _regex_arguments _cmd /$'[^\0]##\0'/ \( /$'word1(a|b|c)\0'/ ':word:first word:(w
|
||||||
'|' /$'word22(a|b|c)\0'/ ':word:second word:(word22a word22b word22c)' \) \)
|
'|' /$'word22(a|b|c)\0'/ ':word:second word:(word22a word22b word22c)' \) \)
|
||||||
_cmd "$@"
|
_cmd "$@"
|
||||||
#+END_SRC
|
#+END_SRC
|
||||||
In this example, the command itself is matched first (any non-empty word). The first argument
|
in this case the first word can be word1 or word11 followed by an a, b or c, and if the first word contains 11 then a second
|
||||||
can be either =word1(a|b|c)= or =word11(a|b|c)=. If the first argument matches the =word11=
|
word is allowed which can be word2 or word22 followed by and a, b, or c.
|
||||||
variant, a second argument becomes available, which can be either =word2(a|b|c)= or
|
|
||||||
=word22(a|b|c)=.
|
|
||||||
|
|
||||||
If this sounds too complicated a much simpler alternative is to use the _regex_words function for creating
|
If this sounds too complicated a much simpler alternative is to use the _regex_words function for creating
|
||||||
specifications for _regex_arguments.
|
specifications for _regex_arguments.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue