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
Fix R reading files #11436
Comments
comment:1
In fact, the file part of what we use doesn't even seem to be necessary. The option we need is
|
comment:2
Yes, and this fixes the original problem too. The only issue is that
So the idea is perhaps that we do NOT see the output from such an evaluation. The problem is that then one has to know that one should assign the big computation to a name via What is the best solution here? To change the reading of lines or to make the documentation REALLY clear? My preference would be to have long commands still output, just like short commands; it seems unfair to have them suddenly do this. |
Based on 4.4.4, but hopefully still applies... |
comment:3
Attachment: trac_11436.patch.gz Possible patch uploaded. Probably needs more documentation, but it fixed my problem locally so I'm going to bed. Suggestions welcome. |
Author: Karl-Dieter Crisman |
Changed keywords from none to r-project |
comment:5
See this sage-devel thread for what I believe is this same problem. |
The current way we configure the R Pexpect interface is to have a 1024 character cutoff to trying to read from a file.
Problem: this doesn't actually seem to work.
jhpalmieri helped track this down. See this sage-support thread for more details.
Helpful links:
It seems like everything is creating files as should be, and using the verbose option to source shows that at least something's being computed, but the result is not showing up in Sage, possibly due to misuse of "source", or "file".
CC: @jhpalmieri @jasongrout @williamstein
Component: interfaces
Keywords: r-project
Author: Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/11436
The text was updated successfully, but these errors were encountered: