Commits on Apr 11, 2017
  1. Preserve the position of (point) after evaling

    After evaling the last expression, if not inserting its value into
    buffer, leave (point) at its original position.
    diogofsr committed with Apr 11, 2017
  2. Eval last expression even after a comment char

    Scan for beginning and end of a sexp, instead of using (point) as the
    Previously, if (point) was after a comment character, the REPL would
    diogofsr committed with Apr 11, 2017
Commits on Mar 26, 2017
Commits on Mar 21, 2017
  1. Don't assign the (field t) property to old REPL inputs

    Previously, Geiser added a (field t) property to inputs before adding
    them to the REPL history so it can determine what characters in the
    buffer belong to old input and yank it when a user pressed
    enter (geiser-repl--maybe-send) on it. When users recalled an old
    input with "M-p" (comint-previous-matching-input-from-input), the old
    input with its (field t) property were inserted after the current
    prompt. Since old inputs were not "front-sticky," when point was just
    after the current prompt but before the characters of the old input,
    Emacs considered point to be outside of the (field t) field; this
    prevented users from using some movement commands such as forward-word
    to move point into the old input text. Furthermore, when users
    inserted text before the old input or yanked other old inputs
    afterwards, this new text did not have the field property and so Emacs
    restricted point movement to and from the old text with the (field t)
    This resolves the issue by not adding the (field t) property to old
    inputs and instead leverages comint's ability to assign the output
    field to all non-input (by setting comint-use-prompt-regexp to
    nil). It should resolve the issue reported in "[Geiser-users] Problem
    with prompt at history item" by Hamish Ivey-Law
    jamescdericco committed Mar 21, 2017
Commits on Feb 1, 2017
  1. A note on dir-locals and load-path variables

    With that in the documentation, i'd taken less time to remember the
    very existence of geiser-guile-load-path, and the fact that paths are
    added also to the compiled load path... but then i guess it's nice to
    re-read my code once in a while.
    committed Feb 1, 2017
Commits on Jan 27, 2017
  1. bug fix: error message get displayed

    Chaos Eternal committed Jan 27, 2017
Commits on Jan 17, 2017
  1. Not inserting a trailing \n when eval prefix is empty

    And, on reflection, it's better we do the same thing with the ERROR
    committed Jan 17, 2017
Commits on Jan 13, 2017
  1. Make eval-last-sexp-to-buffer customizable

    Chaos Eternal committed Jan 12, 2017
Commits on Dec 3, 2016
  1. Bug fix: expanding file name at the right time

    We were expanding the path of files to be loaded at the wrong place in
    the wrong way.  This should be better and address bug #196.
    committed Dec 3, 2016
Commits on Nov 26, 2016
  1. fix malformed argument lists.

    Emacs trunk does not support arguments list like (lambda (&rest) nil)
    anymore, which breaks geiser and errors with "Invalid function: "
    peterwang committed Nov 26, 2016
  2. Make guile's load-file happier with ~ abrevs

    An attempt to address #194.
    committed Nov 26, 2016
Commits on Nov 9, 2016
Commits on Oct 24, 2016
  1. Missing chibi and chez support files

    Should fix #188, and i'm not generating a new version for this unless
    some distribution maintainer is asking.
    committed Oct 24, 2016
Commits on Oct 10, 2016
  1. chez, chibi and mit belong into geiser-active-implementations

    At least by default.
    committed Oct 10, 2016
Commits on Oct 6, 2016
  1. Release 0.9

    committed Oct 5, 2016
Commits on Oct 2, 2016
  1. racket: indentation for 'shared'

    committed Oct 2, 2016
Commits on Sep 30, 2016
  1. Use (car (process-lines ...)) instead of (shell-command ...)

    `shell-command` assumes Bourne-shell-compatible quoting, which
    doesn't work when the user isn't using a Bourne-compatible shell.
    Instead of futzing about with quoting, we can just use `process-lines`
    to execute a process and pass it arguments directly.
    mrhmouse committed with Sep 21, 2016
Commits on Sep 21, 2016
Commits on Sep 17, 2016
  1. Allows Chicken to limit the number of symbols provided to Geiser

    - Also cleaned up the namespace a little.
    dleslie committed Sep 17, 2016
Commits on Sep 6, 2016
  1. Add link to project homepage

    C-h P (`display-package') can make use of it.
    xuchunyang committed Sep 6, 2016
  2. Fix link to melpa-stable

    xuchunyang committed Sep 6, 2016
Commits on Aug 29, 2016
  1. Pacify byte-compiler a bit

    fice-t committed with Aug 14, 2016
Commits on Aug 25, 2016
  1. Not signalling errors for company-mode completions

    ... so that we don't interfere with other active backends, and following
    the same policy as in the rest of company-mode geiser methods. See also
    the discussion in github's #173.
    committed Aug 25, 2016
Commits on Aug 24, 2016
  1. Making autodoc failures silent

    As requested in github issue #173.  Seems it's confusing people, which
    is exactly the problem it was originally trying to avoid!
    committed Aug 24, 2016
Commits on Aug 11, 2016
  1. Adds required modules to binary parameters

    -This causes chicken to fail to run if it cannot find the required
     modules for Geiser; and will tell the user that the module is missing.
    dleslie committed Aug 9, 2016
  2. Disable aggressive prefix assumption

    This was causing significant typing delay with little to no benefit.
    Disabled until a better solution can be found.
    dleslie committed Aug 9, 2016
  3. Remove compilation of chicken module

    This was causing confusion and bug reports on a semi-regular
    basis. Disable it for now until a better solution is made.
    dleslie committed Aug 9, 2016
  4. Minor typo

    dleslie committed Feb 16, 2016
Commits on Jul 26, 2016
  1. README as an org file

    committed Jul 26, 2016