For redirect_stderr you can use a task to read the error output, see: https://groups.google.com/d/msg/julia-dev/1E6ag2Tfs9Q/LLsXMFvd0ugJ
> It will not solve my problem. I have to write technical documents in MS Word (with hundreds of embedded calculations) I understand there may be many external constraints, as well as the established workflow, but two points of information for future consideration: 1. IJulia supports both inline code and LaTeX 2. one could potentially transform the notebook to MS Word format using pandoc, as is done for PDF by IPython/IJulia (admittedly untested for MS Word from IJulia, to my knowledge) http://johnmacfarlane.net/pandoc/ On Sat, Mar 8, 2014 at 8:19 PM, Laszlo Hars <[email protected]> wrote: > > > `parse()` first, then syntax errors are returned > Nothing is returned, if there was a parse error. However, I can catch the > error with try/catch. This is what I meant with "graceful error > handling". Also, it only works with string arguments, not with expressions. > As I said, passing nested strings inside the string argument is hard, and > handling multi-line strings is ugly. > > > try out IJulia > It will not solve my problem. I have to write technical documents in MS > Word (with hundreds of embedded calculations), and constantly switching > applications and cutting-and-pasting text just drives me crazy. As I said, > the Word-Julia interface I made (with an AutoHotkey script) works, but it > is ugly. > > I would really appreciate if someone could answer my questions. >
