Hi "drl", you say that your text terminal's default is black background and dark blue text, and if I understand correctly, you don't like that Sage is using your own default color scheme. If your question is how to change the color scheme of your text terminal then I guess it depends on your computer's operating system. I'm using black on light-yellow.
Not showing error tracebacks means withholding very useful information. There is not just "a few" people doing development in Sage, and for a developer, having that information is essential. Opening a log file on each single of the myriads of errors that may occur in a development process is just awkward. On the other hand, a user who doesn't do development can still look at the bottom line, i.e., the error message, and ignore the traceback. But the error message itself typically doesn't tell if the error is because of a bug or because of wrong usage. So, even for a casual user it makes sense to at least have a short glance at the traceback. While I think tracebacks should always be shown in the text terminal, it might be a good idea to make it so that a traceback in the *notebook* will be folded and will only be visible when the user clicks on an appropriate button. I don't know how that could be done in the Jupyter notebook, but perhaps other people know. A user who decided to wrongly believe that tracebacks are useless won't be bothered, and a developer can easily enough access the traceback. Best regards, Simon On 2018-10-31, deSitter <antimatter3...@gmail.com> wrote: > While I'm bitching - every error generates a blizzard of pointless > information that belongs in a log file, not in front of the user's > eyeballs. That also desperately needs to be fixed. > > On Wednesday, October 31, 2018 at 7:21:34 AM UTC-4, deSitter wrote: >> >> My text terminal uses a black background. The default text is dark blue on >> jet black. This is not a winning start to 8.4. How do I change the text >> color. Seriously, this is the sort of little thing that is absolutely >> exasperating, to get a perfect build right out of the box and then find it >> unreadable and so unusable. What Sage really needs is someone to fix these >> usage issues and make the thing presentable and the syntax less brittle! >> I'm not busy at the moment. Contact me, believe me, I will fix this. >> >> -drl >> > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
