[qitab-devel] default (interactive) output mode for run in inferior-shell
Hi, I found in README of inferior-shell, it is said that the default output mode is as follow: NIL (default) for inheriting the parent process's stdout, But in recent uiop implementation, the ":output nil" means to redirect to /dev/null, while ":output :interactive" means to inherate the parent process's stdout (at least for sbcl). So I think we should change the default value of output parameter for run or change the README. What do you think about that? Best Regards, Huang Ying
Dear Huang Ying,
I found in README of inferior-shell, it is said that the default output mode is as follow:
NIL (default) for inheriting the parent process's stdout,
But in recent uiop implementation, the ":output nil" means to redirect to /dev/null, while ":output :interactive" means to inherate the parent process's stdout (at least for sbcl).
So I think we should change the default value of output parameter for run or change the README.
What do you think about that?
Thanks for the bug report. I've slightly edited the README for now. And some people claim that the concept of "bitrot" is impossible! —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org [A] Computer [programming] language is inherently a pun — [it] needs to be interpreted by both men & machines. — hbaker
Most shell programs (bash etc) use "inherit from parent" as default, why inferior use "redirect to /dev/null" as default? Best Regards, Huang Ying On Wed, Jan 22, 2014 at 12:33 AM, Faré <fahree@gmail.com> wrote:
Dear Huang Ying,
I found in README of inferior-shell, it is said that the default output mode is as follow:
NIL (default) for inheriting the parent process's stdout,
But in recent uiop implementation, the ":output nil" means to redirect to /dev/null, while ":output :interactive" means to inherate the parent process's stdout (at least for sbcl).
So I think we should change the default value of output parameter for run or change the README.
What do you think about that?
Thanks for the bug report. I've slightly edited the README for now. And some people claim that the concept of "bitrot" is impossible!
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org [A] Computer [programming] language is inherently a pun — [it] needs to be interpreted by both men & machines. — hbaker
On Wed, Jan 22, 2014 at 5:21 PM, huang ying <huang.ying.caritas@gmail.com> wrote:
Most shell programs (bash etc) use "inherit from parent" as default, why inferior use "redirect to /dev/null" as default?
That's a good question. Probably because I'm using inferior-shell at the SLIME REPL, and that the parent streams are then on their own inferior-lisp emacs buffer, at which point :interactive as the default is confusing. Also, there was a point at which :interactive did something magic with the input — which is only a bit less the case now, but still. Also, that's a bad default to have in a multithreaded setting. I suppose I could change function run-spec in run.lisp to have an explicit keyword argument (output :interactive) and pass it to run-program. Does anyone else care to comment? Is anyone else using inferior-shell, and would filled with either joy or sorrow at such a change? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Panties: not best thing on earth, but next to it.
participants (2)
-
Faré -
huang ying