On 22 April 2012 00:16, Keshav Kini wrote:
> This is not directly relevant but might be useful for you if you're a
> Firefox user. It certainly is for me.
>
> https://addons.mozilla.org/en-US/firefox/addon/lazarus-form-recovery/
>
> -Keshav
>
Thanks for the suggestion -- and there's a version of
This is not directly relevant but might be useful for you if you're a
Firefox user. It certainly is for me.
https://addons.mozilla.org/en-US/firefox/addon/lazarus-form-recovery/
-Keshav
Join us in #sagemath on irc.freenode.net !
--
To post to this group, send an email to sage-devel@googl
On 21 April 2012 19:37, David Roe wrote:
> I've seen this as well, but I don't know what causes it.
I am managing by using the wysiwyg box instead, which I would normally avoid.
The other thing which annoys me about trac which happens a lot when
several people are working on one ticket at the sa
I've seen this as well, but I don't know what causes it.
David
On Sat, Apr 21, 2012 at 04:13, John Cremona wrote:
> After some recent changes in the trac version we use (I think) I find
> the following, but only when I use it with chromium on my small-screen
> netbook: The text box into which o
After some recent changes in the trac version we use (I think) I find
the following, but only when I use it with chromium on my small-screen
netbook: The text box into which one types comments is extremely
narrow, exactly 3 characters in fact (the same width as the words
"wysisyg" and "textarea" w
Pick
Go to this trac page
http://trac.sagemath.org/sage_trac/report
then pick:
{12} Notebook Tickets needing work
which directs to:
http://trac.sagemath.org/sage_trac/report/12
which generates an error:
Report execution failed: syntax error at or near "p" LINE 5: ...t.priority AND
p.type='p
