-
Notifications
You must be signed in to change notification settings - Fork 19
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
Issue with Codeium in Rstudio Server http://10.10.196.55:8787/ #43
Comments
I also try this :
|
Then i also try in Chrome. It's still not working. : ( |
We haven't tested/explicitly supported RStudio web, so this is probably expected. Do you know what type of text editor library it's using? |
as i know , it is a proprietary component of the RStudio Integrated Development Environment . : (
2454888366
***@***.***
…------------------ 原始邮件 ------------------
发件人: "Prem ***@***.***>;
发送时间: 2023年12月2日(星期六) 凌晨5:02
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [Exafunction/codeium-chrome] Issue with Codeium in Rstudio Server http://10.10.196.55:8787/ (Issue #43)
We haven't tested/explicitly supported RStudio web, so this is probably expected. Do you know what type of text editor library it's using?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I hope this email finds you well. My name is Tianrui, I am a new user about Codeium. I installed this plugin on edge browser,I want to use this plug-in on the Rstudio server web page, the URL is http://10.10.196.55:8787/.
I tried adding the following content to the Allowlist in the settings: http://10.10.196.55.* or 10.10.196.55.*
But it still doesn't work,I don't know if it's because I set it up wrong, or if it's not working properly due to other circumstances. I really need your help, thank you very much.
Thank you in advance for your assistance.
Best regards,
Tianrui
The text was updated successfully, but these errors were encountered: