new output goes to the front of slime presentations #9
Comments
ghost
assigned 
|
Could not reproduce this. Closing until convinced otherwise. |
|
Hmm, actually, reopening. The issuer should define "in front". The output I get goes before the presentation. Should it go after it? It's questionable... IELM can't be a good comparison in this case since it doesn't use the same REPL for results and output. |
|
João Távora notifications@github.com writes:
Not the issuer, but I agree that output from a subsequent command should If more rationale is needed, consider doing some work at the repl, then Christophe |
|
@csrhodes yes that use case sounds reasonable, in fact, it happens to me quite often. Will have a look, but |
The new tests don't assume that the REPL buffer has actual marker objects indicating the relative positions of output, result and prompt. This work is in preparation of handling issue #9. * slime-repl.el (slime-repl-emit): Propertize the output text with a `slime-repl-output' boolean property. (slime-repl-test-markers): More powerful macro for testing repl text. (slime-check-buffer-contents): Simplified with `slime-repl-test-markers'. (repl-test): tests with no output don't expect these markers. (repl-type-ahead): tests with no output don't expect these markers.
When run without slime-presentations, slime-repl exhibited some test failures. This is a "sanity" fix so the current tests can be used as reference for a possible redesign that eventually fixes slime#9 and maybe implements the behaviour described in slime#84. * .travis.yml (env): Test the slime-repl independently from other contribs like slime-presentations. * slime.el (slime-propertize-region): Add edebug spec. * contrib/slime-repl.el (slime-repl-emit-result): Use `insert-before-markers-and-inherit', and do it before saving `slime-output-end'. (slime-repl-write-string): Fix failing tests by passing `eol' as t to `slime-repl-emit-result'. (slime-repl-test-markers): Friendlier test assertions.
When run without slime-presentations, slime-repl exhibited some test failures. This is a "sanity" fix so the current tests can be used as reference for a possible redesign that eventually fixes slime#9 and maybe implements the behaviour described in slime#84. * .travis.yml (env): Test the slime-repl independently from other contribs like slime-presentations. * slime.el (slime-propertize-region): Add edebug spec. * contrib/slime-presentations.el (pretty-presentation-results): new tests, should be more stable, except on allegro. * contrib/slime-repl.el (slime-repl-emit-result): Use `insert-before-markers-and-inherit', and do it before saving `slime-output-end'. (slime-repl-write-string): Fix failing tests by passing `eol' as t to `slime-repl-emit-result'. (slime-repl-test-markers): Friendlier test assertions. (repl-test-2): Skip for now, unstable without slime-presentations.
When run without slime-presentations, slime-repl exhibited some test failures. This is a "sanity" fix so the current tests can be used as reference for a possible redesign that eventually handles #9 and maybe implements the behaviour described in #84. * .travis.yml (env): Test the slime-repl independently from other contribs like slime-presentations. * slime.el (slime-propertize-region): Add edebug spec. * contrib/slime-presentations.el (pretty-presentation-results): new tests, should be more stable, except on allegro. * contrib/slime-repl.el (slime-repl-emit-result): Use `insert-before-markers-and-inherit', and do it before saving `slime-output-end'. (slime-repl-write-string): Fix failing tests by passing `eol' as t to `slime-repl-emit-result'. (slime-repl-test-markers): Friendlier test assertions. (repl-test-2): Skip for now, unstable without slime-presentations.
bug imported from https://bugs.launchpad.net/slime/+bug/627326
At the repl, type
(make-hash-table) RET, in slime-scratch type(loop repeat 10 (print 'foo)) C-x C-e;the new output will go in front of the presentation for the hash-table.
The text was updated successfully, but these errors were encountered: