On Tue, 26 Jan 2016, Daniel Krenn wrote:
"Tip of the day"? Special command "hints()"?
Essentially +1 for "hints()". However, help() seems to do a similar
thing and maybe the FAQs above should go there? (FWIW, its now the first
time I've looked at it; I would have looked at hints() probably ear
On 2016-01-26 06:58, Jori Mäntysalo wrote:
> On Mon, 25 Jan 2016, Samuel Lelievre wrote:
>
>> When starting the Sage REPL, we currently display the following advice:
>>
>> Type "notebook()" for the browser-based notebook interface.
>> Type "help()" for help.
>>
>> We could add a few more h
On Mon, 25 Jan 2016, Samuel Lelievre wrote:
When starting the Sage REPL, we currently display the following advice:
Type "notebook()" for the browser-based notebook interface.
Type "help()" for help.
We could add a few more hints that answer frequently asked questions:
Type "%disp
On Mon, Jan 25, 2016 at 8:42 PM, Samuel Lelievre
wrote:
> When starting the Sage REPL, we currently display the following advice:
>
> Type "notebook()" for the browser-based notebook interface.
> Type "help()" for help.
>
> We could add a few more hints that answer frequently asked questi
> Like for matrices, to come back to the topic?
Indeed, repr(a_matrix) doesn't follow Python's syntax. And list of
matrices is even worse:
sage: [matrix.ones(4) for i in range(4)]
[
[1 1 1 1] [1 1 1 1] [1 1 1 1] [1 1 1 1]
[1 1 1 1] [1 1 1 1] [1 1 1 1] [1 1 1 1]
[1 1 1 1]
On Sunday, January 24, 2016 at 2:09:20 PM UTC-5, vdelecroix wrote:
>
> Yes, you break the fact that for many objects you can copy/paste the
> output to get your object back
>
Like for matrices, to come back to the topic?
Also, is the Sage output primarily for humans or primarily machine-parsabl
Yes, you break the fact that for many objects you can copy/paste the
output to get your object back
sage: %display plain
sage: integral(gamma(x), x)
integrate(gamma(x), x)
sage: eval("integrate(gamma(x), x)")
integrate(gamma(x), x)
but
sage: %display unicode_art
sage: integrate(gamma(x), x)
⌠
Okay. So let's say that we enable ascii_art by default: is there a
unintended consequence? Or should we just do that?
Nathann
On 24 January 2016 at 19:57, Volker Braun wrote:
> There is no bulletproof way for the program to determine whether the
> terminal can display unicode. But every half-way
There is no bulletproof way for the program to determine whether the
terminal can display unicode. But every half-way recent terminal can, and
we have been using unicode in the startup banner for years without
problems. I'd just assume that it works by default nowadays.
%display unicode_art als
> sage: %display unicode_art
> sage: matrix.block(3,3,[matrix.ones(2)]*9)
Would it be safe to enable unicode_art on startup if it is supported?
Or does it mean that many objects will be displayed with drawings
instead of their usual representation as a consequence?
I am trying to figure out *how*
10 matches
Mail list logo
