https://bugs.kde.org/show_bug.cgi?id=375467
--- Comment #17 from Nikita Sirgienko <warqu...@gmail.com> --- (In reply to Alexander Semke from comment #16) > Wouldn't it be better if the main sage bash script would simply forward the > CLI parameters to sage-ipython. With this we'd simply always call sage with > --simple-promt or the user will provide this parameter explicitly in cantor > settings for sage where the user already has to specify the path for sage. > With this solution it would be up to the sage's user/frontend to specify > this parameter or not and there is no need to always use it as proposed in > your trac ticket. Alexender, I reread my ticket message and maybe I was not quite accurate. The ticket suggest add new option (--simple-prompt), that be passed to ipython, like another ipython forward options for sage. So if you run 'sage --simple-prompt' you have sage with ipython with --simple-prompt option and Sage backend could work with sage output. If you don't specify this option, sage don't forward pass '--simple-prompt' to ipython and then ipython starts with default input handler: prompt_tookit. Sage don't send -gthread, -qthread, -q4thread, -wthread and -pylab always to sage-ipython. Sage do it, only if user specify corresponding options. And my ticket just expand list of this options by adding new option (and new corresponding option too). -- You are receiving this mail because: You are watching all bug changes.
