Can clipr_available() start a process?

[jennybc]

Since clipr_available() calls clipr_available_handler() and that tries to both read and write the clipboard, don't you think a call to clipr_available() could still create problems at CRAN, i.e. it could still tickle some process and leave it running?

Perhaps clipr_available_handler() should look more like this:

clipr_available_handler <- function(...) {
  if (!interactive()) {
    clipr_allow <- as.logical(Sys.getenv("CLIPR_ALLOW", "FALSE"))
    if (!clipr_allow) {
      return(FALSE)
    }
  }
  suppressWarnings({
    read_attempt <- try(read_clip(...), silent = TRUE)
    write_attempt <- try(write_clip(read_attempt, ...), silent = TRUE)
  })
  list(read = read_attempt, write = write_attempt)
}

[jennybc]

I'm not entirely sure what's going on, but my spidey sense says that it is possible this issue explains why gitignore had trouble with CRAN:

ropensci/gitignore#7

[mdlincoln]

Hi @jennybc - thanks so much for your patience with my response. Life intervenes!

Yes, it makes a lot of sense to weave the CLIPR_ALLOW check more deeply throughout the package. I'll incorporate this along with the other suggestions.

[mdlincoln]

Closed with 17bdae6