ropensci / ropensci/dev_guide

Regarding console messages, changes in R-devel

Open
#945 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

content :page_with_curl:
Dominant language
R
Stars
164
Forks
69
Avg merge
5d 23h
Merged PRs (30d)
5

Description

Hello,
this might help simplify things or gives different options in regards to section 1.3.2 Console messages.
I just came across this change in R-devel and it seems R4.6 will ship with a bit more verbosity control (https://cran.r-project.org/doc/manuals/r-devel/NEWS.html):
“… New logical option() quiet, defaulting to false, set to TRUE by R’s command-line option --quiet (and similar), now can be switched during an R session. Prompted by Dirk Eddelbuettel’s proposal in PR#18913.”
It is worth noting that there is already options("verbose") and soon there will be options("quiet").
It also work with R calling from the console R --vanilla --quiet see the discussion in the link to the pull request above.
Kind regards,
Klaus

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review section 1.3.2, “Console messages,” alongside the linked R-devel NEWS entry and PR#18913. Determine whether the guide should mention the new options("quiet") behavior and its relationship to options("verbose") and R --vanilla --quiet; done means the section accurately reflects the relevant R console verbosity controls.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.