Closed GoogleCodeExporter closed 9 years ago
This is known API design issue. Documentation should be fixed.
You should manually specify (rnrs) and (mosh) or (mosh concurrent) within a
SPAWN.
Cc higepon.
(Related to Issue 191.)
Original comment by oku...@gmail.com
on 10 Mar 2011 at 1:15
Issue 191 has been merged into this issue.
Original comment by oku...@gmail.com
on 23 Apr 2011 at 7:42
Currently, any practical use-case will be required to specify
((rnrs) (mosh concurrent) (except (mosh) condition-printer))
as import-spec.
So, we should 1) drop condition-printer from (mosh) or 2) from (mosh
concurrent).
Original comment by oku...@gmail.com
on 23 Apr 2011 at 7:48
Could you drop the condition-printer from (mosh concurrent)?
Original comment by hige...@gmail.com
on 26 Apr 2011 at 1:59
Once psyntax-mosh buildscript updated, i'll take care of further updates
(e.g. update nmosh and test suites)
because there is no safe way to update psyntax-mosh (anyone except higepon...)
Original comment by oku...@gmail.com
on 26 Apr 2011 at 1:41
There is no need to update psyntax-mosh when remove condition printer from
(mosh concurrent).
Am I overlooking something?
Original comment by hige...@gmail.com
on 26 Apr 2011 at 2:08
Hmm, you meant "remove" condition-printer from (mosh concurrent), right?
(I'd take "port" (mosh concurrent)'s condition-printer into (mosh))
Original comment by oku...@gmail.com
on 26 Apr 2011 at 2:28
Fixed.
https://github.com/okuoku/mosh/commit/f296d813436bf8f6554b4e1a105bd791f0bb8512
Original comment by oku...@gmail.com
on 26 Apr 2011 at 3:28
Original issue reported on code.google.com by
amoe...@gmail.com
on 9 Mar 2011 at 6:35