From 14f3383c0da1413a5ae82feb19ac89f01d4b9aad Mon Sep 17 00:00:00 2001 From: Famiu Haque Date: Sat, 7 May 2022 08:57:21 +0600 Subject: fix(api): make `nvim_parse_cmd` work correctly with both range and count It seems range and count can be used together in commands. This PR fixes the behavior of `nvim_parse_cmd` for those cases by removing the mutual exclusivity of "range" and "count". It also removes range line number validation for `nvim_parse_cmd` as it's not its job to validate the command. --- runtime/doc/api.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'runtime') diff --git a/runtime/doc/api.txt b/runtime/doc/api.txt index 242546f87d..50fe60a0fc 100644 --- a/runtime/doc/api.txt +++ b/runtime/doc/api.txt @@ -1782,8 +1782,7 @@ nvim_parse_cmd({str}, {opts}) *nvim_parse_cmd()* item was specified and two elements if both range items were specified. • count: (number) Any || that was supplied to the - command. -1 if command cannot take a count. Mutually - exclusive with "range". + command. -1 if command cannot take a count. • reg: (number) The optional command ||, if specified. Empty string if not specified or if command cannot take a register. -- cgit