On Fri, Jan 9, 2009 at 2:05 PM, philt wrote:
>
> Hello,
>
> I'm running my server with account creation disabled and when I want
> to add a user I restart it briefly with notebook(...,accounts=true)
>
> Stage 1:
> I through the "create a new account" procedure without trying the
> newly created u
Hello,
I'm running my server with account creation disabled and when I want
to add a user I restart it briefly with notebook(...,accounts=true)
Stage 1:
I through the "create a new account" procedure without trying the
newly created user then immediately restarts the server with accounts
disable
Hi Tom Boothby (cc: sage-devel),
Have you noticed that there is something screwy with how the notebook
javascript processes input
lately? It's not noticeable over a very fast connection, but it is
over a slower one.
Basically, if you do
[input some text then press shift-enter]
there is a lo
I admit it wouldn't be for everyone. Initially I tried loading it in
using a GreaseMonkey script but discovered that was too late in the
DOM tree. What would be nice is if one could add plug-ins. Perhaps
they could be loaded using xml files much like Google allows. These
initially could be to pers
On Fri, Jan 9, 2009 at 2:30 AM, Martin Albrecht
wrote:
>
>> Sure. I think that what you want is still orthogonal to the TinyMCE
>> effort, but having another edit widget in the tree "just" for
>> highlighting ought to be well thought out and the burden of
>> maintenance must be taken into account
Em Qui, 2009-01-08 às 14:41 -0800, mabshoff escreveu:
>
> The gcc memory requirements are not consistent, i.e. gcc 3.4.x does
> compile the LinBox extension using about 350 MB peak or so. For gcc
> 4.x it seems that maybe 750 MB is peak consumption. So I am not sure
> what to do, i.e. if we make
bsdz wrote:
> Hi,
>
> I dabbled a little with the vmware version of Sage and was able to
> install EditArea, a javascript syntax highlighting library (http://
> www.cdolivet.net/index.php?page=editArea). It is quite useful when
> editing Python and can be turned on or off. It also allows callback
> Sure. I think that what you want is still orthogonal to the TinyMCE
> effort, but having another edit widget in the tree "just" for
> highlighting ought to be well thought out and the burden of
> maintenance must be taken into account, i.e. if somehow TinyMCE could
> be extended to do Python and
