Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F1 doesn't show help and throws error on dataset autocomplete #2356

Closed
ronblum opened this issue Mar 8, 2018 · 6 comments
Closed

F1 doesn't show help and throws error on dataset autocomplete #2356

ronblum opened this issue Mar 8, 2018 · 6 comments
Assignees

Comments

@ronblum
Copy link
Contributor

ronblum commented Mar 8, 2018

System details

RStudio Edition : Server and Desktop
RStudio Version : 1.1.383, 1.1.423, 1.1.442
OS Version      : Mac, Windows, and Linux variants
R Version       : 3.4.3

Steps to reproduce the problem

  1. Type iris at the console, and wait for help topic autocompletions to appear.
  2. Select an autocompletion with the arrow keys, e.g. iris
  3. Press F1 to see help on the dataset.

Describe the problem in detail

No help appears, and the following error message is displayed at the console:

Error in find.package(if (is.null(package)) loadedNamespaces() else package, :
there is no package called ‘package:datasets’

(Clicked F1 multiple times for screenshot to show error + autocompletion)

iris_no_help

Describe the behavior you expected

Help on the dataset, iris, should appear in the Help pane, with no error message.

Cf. #2261 and #2348.

@jmcphers
Copy link
Member

jmcphers commented Mar 8, 2018

@kevinushey Does it look like we need to extend the fix in #2261 in some way, or is this a different bug?

@kevinushey
Copy link
Contributor

I think this may be a different issue -- I'll take a look.

@kevinushey
Copy link
Contributor

I'm surprised to find out that this actually reproduces back in RStudio v1.0. I guess users don't press F1 when the help menu is showing very often :-)

@kevinushey
Copy link
Contributor

Should be fixed with 1e5e7dc. It looks like we only trimmed the package: prefix in certain code paths; we should be doing that universally.

@jmcphers
Copy link
Member

jmcphers commented Mar 8, 2018

Okay, thanks for jumping on that! Given that it is not a regression in 1.1 and hasn't ever been reported before to the best of my knowledge, I don't intend to backport it (let me know if you disagree).

@jmcphers jmcphers closed this as completed Dec 6, 2019
@jmcphers
Copy link
Member

jmcphers commented Dec 6, 2019

Closing since we appear to have fixed this a couple of years ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants