[sage-support] Re: mathjax big braces not rendering properly on sagenb nor publishing properly

2012-01-28 Thread Jason Grout
On 1/28/12 4:56 AM, LFS wrote: Just adding one more comment for search purposes: If you see your equation being cut off from text field into sage field, it means your translator is using 3 braces in a row {{{ Sage interprets {{{ as the beginning of a sage field. So check your translation. I ha

[sage-support] graph.all_simple_paths bug?

2012-01-28 Thread JStarx
Consider the following: sage: Q = DiGraph({1: {2:'a'}, 2: {1: 'b', 3: 'c'}, 3: {2: 'd'}}) sage: Q.all_simple_paths([1], [2]) [[1, 2], [1, 2, 3, 2]] sage: Q.all_simple_paths([2], [1]) [[2, 1]] First, the documentation to all_simple_paths says that a simple path is one in which no vertex appears tw

[sage-support] Re: @interact and precise movement in Slider control

2012-01-28 Thread Jason Grout
On 1/28/12 11:10 AM, Marshall Hampton wrote: Sounds like Jason has a good solution for you eventually. There are some cruder ways to work around this in the meantime: 1) Customize the values in the slider so they are all "nice". 2) Have a coarse- and fine-tuning slider. The final value used co

[sage-support] Re: mathjax big braces not rendering properly on sagenb nor publishing properly

2012-01-28 Thread Jason Grout
On 1/27/12 1:39 PM, LFS wrote: Yeah - thot that might be cryptic after I posted. Hard to write in this forum. Editors tend to try to "help" you. I would NOT worry unless someone else complains since: * I have been moving stuff from the sagenb site to the canterbury site and now back again. Each h

[sage-support] Re: @interact and precise movement in Slider control

2012-01-28 Thread Marshall Hampton
Sounds like Jason has a good solution for you eventually. There are some cruder ways to work around this in the meantime: 1) Customize the values in the slider so they are all "nice". 2) Have a coarse- and fine-tuning slider. The final value used could be the coarse+fine value. The default fine

[sage-support] Re: mathjax big braces not rendering properly on sagenb nor publishing properly

2012-01-28 Thread LFS
Just adding one more comment for search purposes: If you see your equation being cut off from text field into sage field, it means your translator is using 3 braces in a row {{{ Sage interprets {{{ as the beginning of a sage field. So check your translation. I had this problem using my equation

[sage-support] Re: suggested improvement for simplify_trig

2012-01-28 Thread achrzesz
On Jan 25, 6:21 pm, William Stein wrote: > On Wed, Jan 25, 2012 at 7:25 AM, kcrisman wrote: > > >> > Probably that should be implemented inside the trigonometric functions > >> > code itself, instead of in any of the "simplify"'s. > > >> > What do you think? > > >> +1 > > >> It's indeed annoyin

[sage-support] Re: ImportError: No module named sage.all

2012-01-28 Thread Simon King
Hi Andrey, On 27 Jan., 14:13, Andrey Abramov wrote: > hexxy@hexxy-PC:/var/www/codes/codetables$ python2.6 gen_pol_other.py Let me guess: python2.6 is some system-wide installation of Python, right? Sage has its own Python, and I guess that your system-wide python2.6 simply has nothing to do wit

[sage-support] Re: mathjax big braces not rendering properly on sagenb nor publishing properly

2012-01-28 Thread LFS
Found problem. The mathjax works great if all equations are properly input! However in sage editor, if you have an open tag and you edit before the end tag, it will sometimes do a "dreamweaver" thing of closing the tag and reopening it. You cannot see this in the editor. This may happen even if