Gábor Csárdi

Good point. I "fixed" seer, to install `falsy` form GitHub automatically.

I'll just archive this, once crandb does not need it.

Actually, that's not the right example, because the backslashes should have been doubled. Here is a problematic example: ```r r"{"}" eval(parse(text = '{r"{"}"}')) glue::glue('{r"{"}"}') ``` ``` ❯ r"{"}" [1] "\""...

It is this from rlang: ```r mark_emph("{foo {}") #> [1] "{.emph {\"{foo {}\"}}" cli::format_message(mark_emph("{foo {}")) #> Error in glue_data(.x = NULL, ..., .sep = .sep, .envir = .envir, .open =...

I am seeing this as well. It was working for a couple of weeks, and then the network was gone, so I rebooted it, and now it does not boot...

I doubt that the issue is with rmarkdown. It must be something weird in the R-hub check environment, because I also can't reproduce it as a normal user on that...

@dpeterson71 This is a bit late, but set the `NO_COLOR` env var to `true` and then all formatting is removed.

Isn't this the usual thing, the strange order of the `search()` path? `[

Remove all these symbols from `e1` and then `e` will be GC-d: ```r ❯ ls(environment(e1), all.names = TRUE) [1] "..." ".Class" ".Generic" ".GenericCallEnv" [5] ".GenericDefEnv" ".Group" ".Method" ``` Actually, scratch...

> But when I poke at it, I don't see how . holds a reference to e. `.` is the piped data in the pipe, so I guess `.` is...