>
> help() with parameters to show longer help? (And smaller default than
> help() now prints.)
help() could definitely be more helpful on concepts. For instance, the
typesetting we're talking about here could appear if you typed
`help("terminal")` or something. There could be a list of predefine
What about having an option at startup?
Something like:
sagestarts the command line interface with nice unicode
sage -ascii starts the command line interface with the old style (for
the user cases mentioned here: blind people, copy-paste able output and so
on)
El doming
On Monday, January 25, 2016 at 8:42:45 PM UTC-5, Samuel Lelievre wrote:
>
> Type "%display unicode_art" for a nicer display of some outputs.
>
We know that this is ugly but if you dig into the documentation you'll be
able to find better-looking settings, promise!
--
You received this messag
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
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 "%display unicode_art" for a nicer display of some ou
On Sunday, January 24, 2016 at 6:33:00 PM UTC-5, Nils Bruin wrote:
>
> For attracting novice users who care about presentation of results, I
> would guess the terminal-based output is basically irrelevant.
>
And by making the terminal UI as unwelcoming as possible we can ensure that
it stays ou
On Sunday, January 24, 2016 at 1:46:34 PM UTC-8, Volker Braun wrote:
>
> Yes you can set it up the way you want, this is about what a sane DEFAULT
> is. And the best machine parseable output is, like the best output for the
> visually impared, not the best output for the majority of our potential
Yes you can set it up the way you want, this is about what a sane DEFAULT
is. And the best machine parseable output is, like the best output for the
visually impared, not the best output for the majority of our potential
users. On the plus side they will never become our users as long as we try
You can always setup your Sage to your custom preferences by adding things
to "~/.sage/init.sage". In this case, just add "%display unicode_art".
Best,
Travis
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and st
On Sunday, January 24, 2016 at 9:10:27 AM UTC-8, Nathann Cohen wrote:
>
> Hello everybody,
>
> I just noticed that M.str(unicode=True) (when M is a matrix) prints the
> matrix very nicely (especially when it is a block matrix), with pretty
> parentheses on both sides.
>
> sage: print matrix.b
> 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*
Vincent Delecroix wrote:
> At least you can do
>
> sage: from sage.repl.rich_output import get_display_manager
> sage: dm = get_display_manager()
> sage: dm.text = 'unicode_art'
...or
sage: %display unicode_art
sage: matrix.block(3,3,[matrix.ones(2)]*9)
⎛
20 matches
Mail list logo
