1. 03 Oct, 2014 1 commit
  2. 20 Sep, 2014 3 commits
  3. 15 Jul, 2014 2 commits
    • Christophe Rhodes's avatar
      add `swank:apropos-list-for-emacs` · df701650
      Christophe Rhodes authored
      and also `swank:describe-definition-for-emacs`, helping to make it
      useful.  It's still a bit weird with the confusion between name of
      thing, name of help file, and so on (and also because
      describe-definition-for-emacs must return a definition kind from a
      restricted set defined in base slime) but it's basically working.
      df701650
    • Christophe Rhodes's avatar
      add `swank:clear-repl-variables` · 04218c0c
      Christophe Rhodes authored
      null implementation (we don't have any repl variables)
      04218c0c
  4. 20 Apr, 2014 2 commits
  5. 14 Mar, 2014 1 commit
  6. 11 Jan, 2014 4 commits
  7. 29 Nov, 2012 1 commit
    • Christophe Rhodes's avatar
      more srcref frobbing · 22705b4a
      Christophe Rhodes authored
      I do not pretend to understand whether this is new, but in 2.14
      parsing an expression, in addition to adding srcref attributes to the
      results of the parse, can result in actual srcref elements being in
      the results.  Those srcrefs also need to be frobbed so that display of
      functions at the repl works properly.  (I do think this worked in 2.12
      without this extra frobbing, but I am totally prepared to admit that I
      can't really remember).
      
      Since we're on the case, also frob things that look like srcrefs but
      aren't under "srcref" attributes, such as "wholeSrcref"s
      22705b4a
  8. 20 Nov, 2012 1 commit
    • Christophe Rhodes's avatar
      fix compilation of x[y,] · cc42bfe8
      Christophe Rhodes authored
      Oh boy.  I do not pretend to totally understand what is going on, but
      what seemed to be happening is that somehow when walking the parse
      tree to adjust srcrefs to the real file position rather than the
      string position, the `empty' space in x[y,] was turning from a
      zero-element name to a missing object, and then subsequent attempts to
      evaluate the missing object (or even return it) were failing.
      
      The workaround is to short-circuit the process for name objects, which
      are atomic and (empirically) do not have srcrefs attached anyway and
      so can be returned without modification.
      cc42bfe8
  9. 17 Sep, 2012 1 commit
  10. 01 May, 2012 2 commits
  11. 29 Apr, 2012 2 commits
    • Christophe Rhodes's avatar
      rework `swank:simple-completions` · f198b5e4
      Christophe Rhodes authored
      In the process, implement looking up foo$bar$baz, and passing those
      completions back.  It's not completely robust to somewhat exotic
      syntax, as it assumes that the text being completed can be used
      directly as character vectors naming objects or fields; it is good
      enough to get started, and now a lot less annoying to
      use (particularly when lots of fields have underscores in them...)
      f198b5e4
    • Christophe Rhodes's avatar
      log wishlist completion bug · 62734d71
      Christophe Rhodes authored
      Also note some other bugs as fixed.
      62734d71
  12. 24 Apr, 2012 2 commits
    • Christophe Rhodes's avatar
      declare a version in `swank:connection-info` · 2b906424
      Christophe Rhodes authored
      Useful both for me, to track what slime version is most likely to be
      maximally compatible, and for SLIMV users, which dispatch on the
      version to know whether the protocol is byte-count-based or
      character-count-based.
      2b906424
    • Christophe Rhodes's avatar
      implement `swank:operator-arglist` properly · f26811f3
      Christophe Rhodes authored
      Now that slime-operator-at-point is overrideable, I can even test this
      from within Emacs -- but thanks to Philipp Marek for implementing this
      in his SLIMV-based environment first.
      f26811f3
  13. 23 Apr, 2012 2 commits
    • Christophe Rhodes's avatar
      fix bug #21 · 24bb738d
      Christophe Rhodes authored
      %in% needs a `vector' first argument, so make it so, listifying
      anything that isn't already a vector.  (Note: there seem to be plenty
      of non-vector first arguments that work, such as
      as.Date("2012-01-01"), which returns FALSE to is.vector() -- but the new
      code seems to get that right anyway, based on very limited testing.
      24bb738d
    • Christophe Rhodes's avatar
      log bug #21, regarding inspection of environments · 14bc3a0d
      Christophe Rhodes authored
      Reported by Philipp Marek
      14bc3a0d
  14. 15 Dec, 2011 1 commit
  15. 09 Dec, 2011 3 commits
  16. 23 Oct, 2011 4 commits
  17. 19 Sep, 2011 2 commits
  18. 13 Sep, 2011 3 commits
  19. 10 Sep, 2011 3 commits