8 Commits

Author SHA1 Message Date
Ingo Karkat 622fd58722 ingo#cmdargs#command#Parse: Documentation: BUG: commandCommands and range result elements are swapped 2023-05-15 17:13:34 +02:00
Ingo Karkat 69604afd81 Cosmetics: Delete changelog and dependency 2020-03-10 16:49:57 +01:00
Ingo Karkat 8a113147ea FIX: Also include unprintable characters (e.g. ^G) in ingo#cmdargs#command#DelimiterExpr()
So that clients like CmdlineSpecialEdits#Substitute#ChangeSeparator() correctly extract the :substitute arguments in :s^Gfoo^Gbar^Ggc (which is a valid command and works). (Unprintable separator characters are unlikely to be used elsewhere, though.)
Need to exclude <Tab> now as well; use the [[:space:]] collection for that.
2020-03-10 16:33:15 +01:00
Ingo Karkat d1f9adf7fa ingo#cmdargs#command#Parse(): Support special a:argumentExpr value of "*" that parses any regular command argument
To avoid that clients have to supply the cumbersome regular expression for non-command separator characters.
2019-04-04 15:36:35 +02:00
Ingo Karkat 14a3e530b0 ingo#cmdargs#command#Parse(): Documentation: Clarify a:argumentExpr 2019-04-04 15:30:48 +02:00
Ingo Karkat d03b5afd30 ingo#cmdargs#command#Parse(): Improve parsing of command sequences
This somehow previously failed when there's whitespace between a previous command and the | delimiter:
:echo ingo#cmdargs#command#Parse('new|verbose s /foo/bar/g', '.*$') " OK
:echo ingo#cmdargs#command#Parse('new |verbose s /foo/bar/g', '.*$') " FAIL: Parses "new" as command.

The cause is that /^\s*/ yields an empty match instead of /\\\@<!|\s*/ matching. Break the parsing into two iterations, and try with the |-separation first. This should also make troubleshooting easier, as we now use more intermediate variables.
2017-11-21 11:46:03 +01:00
Ingo Karkat 71248716fb Documentation: ingo#cmdargs#command#Parse(): Document re-assembly 2017-11-21 11:45:25 +01:00
Ingo Karkat ca60ad060d file creation 2017-05-26 17:43:44 +02:00