REditorSupport / REditorSupport/vscode-R
Folder with French characters like "é" prevent the R objects from being displayed in the R Tab
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 5
Description
Describe the bug
When I open a folder with an accent such as "é" and work with a R script within the folder, the variables are not displayed in the R tab.
To Reproduce
Steps to reproduce the behavior:
- Create a folder with an accent
- Create an R script within
- Execute a line of code creating an object
- Go to the R tab
Can you fix this issue by yourself? (We appreciate the help)
Yes, I just rename the folder
(If yes,) can we assist you with anything?
(If applicable) Please attach setting.json
// R.exe path for windows
"r.rterm.windows": "",
// R path for Mac OS X
"r.rterm.mac": "/usr/local/bin/R",
// R path for Linux
"r.rterm.linux": "/usr/bin/R",
// R command line options (i.e: --vanilla)
"r.rterm.option": [],
// An optional encoding to pass to R when executing the file, i.e. 'source(FILE, encoding=ENCODING)'
"r.source.encoding": "UTF-8",
// Keeping focus when running
"r.source.focus": "editor",
// Use active terminal for all commands, rather than creating a new R terminal
"r.alwaysUseActiveTerminal": false,
// Use bracketed paste mode
"r.bracketedPaste": false,
// Enable R session watcher
"r.sessionWatcher": true,
// Delay in milliseconds before sending each line to rterm (only applies if r.bracketedPaste is false)
"r.rtermSendDelay": 8,
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
You can show the keyboard contents by pressing F1 and Developer: toggle screencast mode
Environment (please complete the following information):
- OS: [e.g. Windows, macOS, Linux]
- VSCode Version: [e.g. 1.42.0]
- R Version: [e.g. 3.6.2]
- vscode-R version: [e.g. 1.2.2]
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by creating an accented folder, running an R script that creates an object, and checking the R tab with the session watcher enabled. Start by tracing the R tab and session watcher behavior around the folder path; done means objects are displayed when the workspace path contains characters such as é.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100