1. 23 Oct, 2011 1 commit
  2. 19 Sep, 2011 1 commit
  3. 13 Sep, 2011 1 commit
  4. 10 Sep, 2011 2 commits
  5. 20 Aug, 2011 1 commit
  6. 06 Apr, 2011 6 commits
  7. 08 Oct, 2010 2 commits
    • Christophe Rhodes's avatar
      capture output from evaluating swank requests · d71a2190
      Christophe Rhodes authored
      This fixes bug #1.  It is somewhat on the risky side given that there
      are current known protocol problems in the presence of non-ASCII
      encodings, but it does make working in the slime repl much more
    • Christophe Rhodes's avatar
      srcrefs in swank:compile-string-for-emacs · 16e6dc8f
      Christophe Rhodes authored
      Wow, this was hard.  parse() constructs a vector with mode
      "expression", consisting of multiple, possibly nested calls.
      Scattered throughout this structure are srcrefs with absolute
      locations.  This means that we need to walk the parsed data structure
      and adjust every srcref that we can find, giving it an offset based on
      the location information passed to compile-string-for-emacs (which
      requires bleeding-edge 2010-10-08 slime, because earlier versions
      don't pass line/column information in the position argument).
      But we can't simply adjust the "srcref" attribute on our parsed data
      structure, because R tries very hard to be pure.  Instead we need to
      return a copy with the right modifications (but preserving everything
      else of importance).  It's straightforward once you know how, but
      there were many painful missteps to get to this point.  Still, now
      M-. works on function names assigned with C-c C-c in source buffers.
  8. 07 Oct, 2010 3 commits
  9. 01 Oct, 2010 3 commits
  10. 16 Sep, 2010 1 commit
  11. 12 Sep, 2010 3 commits
  12. 11 Sep, 2010 1 commit
  13. 10 Sep, 2010 1 commit
  14. 09 Sep, 2010 4 commits
  15. 07 Sep, 2010 2 commits
  16. 03 Sep, 2010 3 commits
    • Christophe Rhodes's avatar
      swank:value-for-editing and swank:commit-edited-value · df9e80e0
      Christophe Rhodes authored
      These are (in principle, at least) really, really easy.
    • Christophe Rhodes's avatar
      alternative printing for the REPL · f3a32de1
      Christophe Rhodes authored
      instead of using print(), use str().  Also, be even more cautious
      about cleaning up in printToString; previously, errors in printing
      would lead to a sink to a closed fifo...
      Printing is still not really right, and I forsee that we will end up
      writing our own printer to get something more lispy.  But at least
      this approach tends not to dump huge tables into the REPL.
    • Christophe Rhodes's avatar
      integrate into R's event loop, possibly · ab6021d4
      Christophe Rhodes authored
      in readPacket, call socketSelect() before actually trying to read on
      the connection.  This seems to allow R to update graphics windows and
      other such niceties.
      It would be nice to be able to preserve the (inferior) R REPL as well,
      but I haven't yet discovered whether that's possible.
  17. 01 Sep, 2010 2 commits
  18. 31 Aug, 2010 1 commit
    • Christophe Rhodes's avatar
      initial implementation of support for REPL presentations · e35149b4
      Christophe Rhodes authored
      There's a lot here that's ugly, unfinished or just downright horrible.
      Most notably, presentation support depends on swank-side read-time
      evaluation (indicated with Common Lisp syntax, which hilariously is a
      comment in R).  We can't support that in general, but we can
      special-case the presentation-specific operator.
      But then the next difficulty comes along; actually performing that
      read-time evaluation needs to happen in a different environment than
      the evaluation of the REPL form.  In order to achieve this, we abuse
      bquote() the equivalent of Lisp's backquote facility, by calling what
      in CL terms would be its macro-function on the parsed, preprocessed
      expression; only after doing that (and hence resolving the `read-time'
      evaluations) do we evaluate the call itself.
      The implementation of presentation protocol messages is also slightly
      ugly; having to implement cl:nth-value is particulraly horrible, but
      the lack of weak references / weak tables in R (at least as far as I
      can tell at the moment) is a cause of niggling concern.
  19. 30 Aug, 2010 2 commits