The `options(continue = " ")` in `.Rprofile` does not take effect in Console.

Open
#3,845 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
r, typescript

Research direction

Reproduce the issue by setting options(continue = " ") in ~/.Rprofile, restarting the R session, and running the multiline command in the Positron Console. Start by tracing the Console entry point that renders continuation prompts; done means multiline input uses the configured blank prompt instead of '+', matching the expected output.

Written by the indexing model from the issue text.

Description

area: console bug lang: r support

Positron Version:

Positron Version: 2024.06.1 (Universal) build 27
Code - OSS Version: 1.90.0
Commit: a893e5b282612ccb2200102957ac38d3c14e5196
Date: 2024-06-26T02:08:06.673Z
Electron: 29.4.0
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.4.0

Steps to reproduce the issue:

  1. Add options(continue = " ") to ~/.Rprofile.
  2. Restart R session.
  3. Run a multi-line command:
mtcars |> 
  ggplot2::ggplot(ggplot2::aes(x = mpg)) +
  ggplot2::geom_histogram()

What did you expect to happen?

I expect the continue lines in console to be blanks rather than the default +. This expected behavior appears in RStudio, but not in Positron.

Want:

> mtcars |> 
   ggplot2::ggplot(ggplot2::aes(x = mpg)) +
   ggplot2::geom_histogram()

Got:

> mtcars |> 
+   ggplot2::ggplot(ggplot2::aes(x = mpg)) +
+   ggplot2::geom_histogram()

Were there any error messages in the output or Developer Tools console?

None.

Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 9h
Merged PRs (30d)
195

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.

More from posit-dev/positron

All issues in posit-dev/positron

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.