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

polyOrg and :session #8

Closed
fkgruber opened this issue Jan 25, 2019 · 2 comments
Closed

polyOrg and :session #8

fkgruber opened this issue Jan 25, 2019 · 2 comments

Comments

@fkgruber
Copy link

Hi
I noticed that poly org seems to be ignoring the :session assign to the block.

Suppose I'm running multiple R session and I specify the code block to use a specific session (or I specify it for the buffer in the header). Then I would think poly org would automatically use the correct session to send the code to. Currently it ask you the first time which session to use and from then on it uses that session.

It seems to me that it would make sense if the :session header should define which R session to use.

thanks
FKG

@vspinu
Copy link
Contributor

vspinu commented Jan 25, 2019

Indeed. All inner modes share same indirect buffer, so it will be connected to one inferior. In principle one can create separate inner modes per session but it would complicate things a bit.

Easier would be to install a hook which would automatically assign a session when you move to an R chunk.

@vspinu vspinu closed this as completed in 9d73c9d May 10, 2019
@vspinu
Copy link
Contributor

vspinu commented May 10, 2019

I have implemented the above mentioned idea. it's not perfect, as it will not detect org session if you start it from inside an R block. If you always start your or sessions from outside of R blocks everything should be fine.

The full proof solutions should be implemented on the ESS side once emacs-ess/ESS#914 is in.

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

No branches or pull requests

2 participants