Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
2007
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 2007

[Date Index] [Thread Index] [Author Index]

Search the Archive

Location of Error Messages (v.6)

  • To: mathgroup at smc.vnet.net
  • Subject: [mg80902] Location of Error Messages (v.6)
  • From: Helen Read <read at math.uvm.edu>
  • Date: Wed, 5 Sep 2007 02:51:27 -0400 (EDT)

In Mathematica 6, some error messages get printed right in the notebook. 
For example, if I execute a cell with a bracketing error, it is 
highlighted, and clicking on the yellow + prints the error message right 
below the cell in question. For other types of errors (for example, type 
in and execute Graphics3D[Arrow]), clicking the yellow + prints the 
error message in a separate message window that's a bit of a nuisance to 
deal with (the window really isn't tall enough, and it's not in a 
convenient place on the monitor). I'd like to have this type of error 
printed in the notebook, which seemed like something one could set in 
the preferences. It doesn't seem to work, however.

In the Preferences, on the Interface tab, under Message and Warning 
Actions, the item in question seems to be "User interface log messages" 
which is by default set to Print to Console. After setting that to Print 
to Input Notebook, clicking on the yellow + does nothing. Setting it to 
Beep and Print to Input Notebook, it does indeed beep, but still does 
not print the message anywhere. Is there a way to get this to work?

Under Message and Warning Actions on the Evaluation tab, both "Kernel 
Messages" and "Print[] command output" are set to Print to Input 
Notebook, if that has any bearing.

--
Helen Read
University of Vermont


  • Prev by Date: Re: Fwd: correction to: more than 1.5 hrs of trying: Grid
  • Next by Date: Kernel and frontend crash with ANY Graphics3D objects
  • Previous by thread: Re: Incorrect, misleading, "Operate Directly on Graphics" example.
  • Next by thread: Kernel and frontend crash with ANY Graphics3D objects