-
Notifications
You must be signed in to change notification settings - Fork 73
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
Customized R prompt not working in Rice #9
Comments
You are right that rice doesn't honor that option. Theoretically, For your second issue, which version of EDIT: Wait, the completion is still not working as expected. |
@randy3k I am using |
The completion issue is fixed at the master branch, I thought I have fixed it but there was a bug. |
OK, waiting for a perfect solution. |
I am now working on the prompt. |
All fixed, |
Oops, it was a false +ve |
I've got the dev version installed now. When ENTER is hitted, a new line is inserted(or, should I say the the input cursor goes to the next line?), is it supposed to be like this? |
Did you force it to install?
|
Problem solved. |
Glad that it also works for you. v0.0.13 is released. |
Nice little tool !
I have a line in my
~/.Rprofile
:to customize the R prompt style and color. It worked in R console and in RStudio daily build(yes, stable build does not support this yet ), but Rice won't parse it.
Another thing is that when I type in Rice, the code completion pops up and I use UP-DOWN arrow key to navigate through all cadidate, but when I hit ENTER, the line will be submitted and ran, which is not good logci. In
zsh
orRStudio
, where code completion is implemented, hitting ENTER will usually just input the code completion candidate you choose, not run it immediatly. This is annoying because when I am typing and using code completion, it usually means the line is not done yet. For example, when I inputlibrary(MA
,MASS
pops up and I navigate to it and hit ENTER, the line will run. However, a right braket is absent and the code definitely won't run properly.The text was updated successfully, but these errors were encountered: