Hello,
We recently started receiving contributions from a user who prefers to
only use their GitHub ID.
I tried this entry in DESCRIPTION (with their actual ID):
person(comment=c(github="@github_user_id"), role="ctb")
But R CMD check complains:
* checking DESCRIPTION meta-information ... NOTE
https://stackoverflow.com/questions/3796436/whats-the-technical-reason-for-lookbehind-assertion-must-be-fixed-length-in-r
On Tue, May 27, 2025, 4:07 PM Josiah Parry wrote:
> Hi all,
>
> I've encountered an issue where using `perl = TRUE` for regular expressions
> with grepl() causes an error on
Thanks all!
Kevin, I think you make a really good point that the lookbehind isn't
necessary. If I'm checking for the termination of /[0-9]+$ that is
sufficient to know that the string ends with that pattern.
On Tue, May 27, 2025 at 3:24 PM Kevin Ushey wrote:
> Hi Josiah,
>
> Why not share a rep
Hi Josiah,
Why not share a reprex / something we can copy and paste to directly
reproduce the issue?
In any case, I suspect this depends on the underlying PCRE
implementation, and so isn't really directly an R issue. You might
have luck if you rewrite your regular expression from:
(?<=(Featu
Hi all,
I've encountered an issue where using `perl = TRUE` for regular expressions
with grepl() causes an error on ubuntu CI runners only.
Is this a known limitation of perl = TRUE for grep and family in base R? Or
is there a suggested workaround?
The issue is specifically with lookbehinds:
PC
I believe the mysterious underused `regexec` is for this:
s = c("foo/bar", "baz/bur", "baz", "bar")
m = regexec("(foo|baz)/(b[au]r)", s)
regmatches(s, m) |> sapply("[", 3)
The `?regex` have some examples for parsing URL using regexec.
-- Jirka
On 28/05/25 10:24, Kevin Ushey wrote:
Hi Josiah,
