[ESS-bugs] ESS[R] file-remote-p: Wrong type argument: stringp, nil

[Vitalie Spinu]

  >> "Sparapani, Rodney" <rsparapa at mcw.edu>
  >> on Fri, 7 Sep 2012 22:16:29 +0000 wrote:

  > C-c C-b ...
  >> > + + + + > >

That is so freaking wired. Invisible evaluation should be very
stable. Where is really no way your output can just disappear.

I have just added a super verbose snapshoting of the process state. 

Please upgrade and set ess-verbose to t. Now go to the end of *ESS*
buffer and monitor the output of your process now in real time.

Please paste here what you see there after C-c C-b. I really hope we can
get to the crux of this one.

    Viatalie

  > At this point, typing C-g doesn't do anything.  The *R* buffer is just frozen
  > with the cursor blinking.
  > ________________________________________
  > From: Vitalie Spinu [spinuvit at gmail.com]
  > Sent: Friday, September 07, 2012 4:36 PM
  > To: Sparapani, Rodney
  > Cc: ess-bugs at r-project.org
  > Subject: Re: [ESS-bugs] ESS[R] file-remote-p: Wrong type argument: stringp, nil

  >> Rodney Sparapani <rsparapa at mcw.edu>
  >> on Fri, 07 Sep 2012 16:28:26 -0500 wrote:

  >> On 09/07/2012 04:13 PM, Vitalie Spinu wrote:
  >> That is very bad. The worst part, is that I cannot reproduce anything.
  >>> 
  >> Does it happen with both visible and invisible evaluation? (C-u C-c C-b)

  >> It works with C-u C-c C-b

  >  I really have to get it word by word from you ;)

  > So, what is C-u is it visible or invisible? In other words what is the
  > value of ess-eval-visibly-p?

  > It looks like it is the visible evaluation which you have trouble
  > with. But I am still not fully understanding what you see. Can you
  > please paste the output of both C-u C-c C-b and C-c C-b?

  > Do you have to C-g to stop the C-c C-b evaluation?

  >     Vitalie