An Existing Use of @inheritParams Broke

[brodieG]

Similar problem to #1347 caused by the fix for #950, but in this case it seems to me the old behavior was correct. We have ?substr:

...
substr(x, start, stop)
substring(text, first, last = 1000000L)
...
Arguments
x, text        a character vector.
start, first   integer. The first element to be extracted or replaced.
...

In fansi I have @inheritParams base::substr, which with previous roxygen2 produced the desired correct outcome.

Would you consider a PR to do a second matching pass to recover the correct old behavior in cases like these? Of course it is the user's responsibility to make sure that inheriting a subset of joint parameters like this makes sense as it does here (less so with e.g. taking just x out of x,y from merge).

A code example showing the failure to inherit:

library(roxygen2)
out <- roc_proc_text(rd_roclet(), "
#' My substr
#'
#' @inheritParams base::substr
#' @param myparam parmesan
mysubstr <- function(x, start, stop, myparam) {}")[[1]]
out$get_value("param")
##   myparam 
## "parmesan" 

vs

#' My substr
#'
#' @inheritParams base::substr
#' @param myparam parmesan
mysubstr <- function(x, start, first, myparam) {}")[[1]]
out$get_value("param")
## > out$get_value("param")
##                                                start,first 
## "integer.  The first element to be extracted or replaced." 
##                                                    myparam 
##                                                 "parmesan" 

[hadley]

I think unfortunately that this comes up infrequently enough that I really don't want to make the existing algorithm more complicated.