posit-dev / posit-dev/positron
Autocomplete favors packages over functions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
System details:
Positron and OS details:
Positron Version: 2025.05.0 (system setup) build 75
Code - OSS Version: 1.99.0
Commit: 6af5bd88e7ff43e833efd238a6a9bc077800059a
Date: 2025-04-22T03:49:41.007Z
Electron: 34.3.2
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045
Interpreter details:
R 4.5
Describe the issue:
I tried to search for a similar issue, but did not find one.
In Positron (or Ark?) it seems like the autocomplete/auto-suggestion prioritize packages over functions. This can be a bit annoying when you are used to Rstudio, where it seems to be the reverse.
The issue is I tab complete to fast and end up getting the wrong completion from what I expected
Steps to reproduce the issue:
In a dplyr pipeline
library(dplyr)
mtcars |> sele [hit tap] -> mtcars |> selectr::
Expected or desired behavior:
mtcars |> sele [hit tap] -> mtcars |> select()
Were there any error messages in the UI, Output panel, or Developer Tools console?
No, but here is a screenshot that illustrates the problem
(positron)
(rstudio)
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
No source file, test, or entry point is named. Start by reproducing the dplyr pipeline completion in Positron or Ark and compare it with RStudio, then identify where package and function suggestions are ranked. Done means typing sele and accepting the completion produces select() rather than selectr::.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100