id summary reporter owner description type status priority milestone component resolution keywords cc merged author reviewer upstream work_issues branch commit dependencies stopgaps
5626 when %latex goes bad in the notebook, it doesn't display the debug/error log anymore was boothby "A user posted this:
{{{
Hi,
I try the following in my first cell in a new notebook with sage-3.4
and the latest Ubuntu 64bit os.
------------------------------------
%latex
Try this: $$x^2=-1$$.
------------------------------------
evaluate
An error occured.
Error latexing slide.
-------------------------------------
(new cell)
-------------------------------------
Thats all I get. I don't get any other latex log output, and it
doesn't write any sage*.dvi files. I've noticed in the sage-support
}}}
Then I responded to explicitly pass in the debug option and ...
{{{
On Sat, Mar 28, 2009 at 6:55 PM, J Elaych <> wrote:
>
>
>> What happens if you type this at the command line:
>>
>> sage: sage.misc.latex.Latex().eval('Try this: $$x^2=-1$$.',0,0,debug=True)
>>
>> William
>
> Awesome, thanks. Latex wasn't finding 'fullpage.sty' so I installed
> 'dblatex' via
> Ubuntu, which in turn installed tons of latex packages, including ../
> preprint/fullpage.sty.
> I see that you have helped other people find fullpage.sty before, but
> the real
> help for me was the pointer to the sage.misc.latex.Latex().eval()
> command.
>
> Thanks again,
It's a bug that you didn't get a traceback in the first place. It's possible thatthis bug was maybe introduced by John Palmieri in this patch:
http://hg.sagemath.org/sage-main/rev/b6c770bd40f8
But it could have also been introduced in a subsequent patch...
-- William
}}}" defect closed major sage-duplicate/invalid/wontfix notebook duplicate N/A