karthik / karthik/Rtools

Auto-completion for R (R.sublime-completion file)

Open
#2 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
33
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Hi,
I am not sure how auto completions work for you but I create a R.sublime-completions file at one point. Here is a description:

http://readthedocs.org/docs/sublime-text-unofficial-documentation/en/latest/extensibility/completions.html?highlight=sublime-completions

So the auto completions come from different sources. One is the sublime-completions file. Check out my R.sublime-completions to see whether such a file improves the auto-complete proposals ST2 makes. I can't really tell whether it makes a difference because it's to long ago that I added this file. Here it is (I think you just have to put it in your packages/R folder:

https://gist.github.com/2336626

Note that this file includes functions that are particular to my packages and my own functions. So it will make suggestions that do not make sense for you occasionally. If such the sublime-completions file improves auto-completion for R, I can send you code for the Rtools package that automatically creates a auto-completion based on the currently loaded packages in R. It's not going to be straight forward to integrate this code in the ST2 package but it would be possible to create a R.sublime-completions for the base and some popular R packages or invest some time to integrate the automatic creation of the file in Rtools.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the R.sublime-completions file described in the issue and the linked gist, placing it in the package's R folder as suggested. Compare Sublime Text 2's R auto-completion proposals with and without the file, then review whether the Rtools-generated completion approach is feasible. Done means documenting the observed improvement and choosing a clear static or generated-completions direction.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.