On Aug 22, 2009, at 9:57 AM, Dr. David Kirkby wrote:
>
> William Stein wrote:
>
>> It's important to clarify what a banner is for, what is "useful
>> information" and for what purpose. First, think about this -- Every
>> time you read a question or bug report from a user, what do you often
>> as
William Stein wrote:
> It's important to clarify what a banner is for, what is "useful
> information" and for what purpose. First, think about this -- Every
> time you read a question or bug report from a user, what do you often
> ask the user?
>
> If it is a build question:
>
> * what
Note the difference between
j...@ubuntu%gp -q
? 2+2
4
and
j...@ubuntu%gp
[13 lines of build info, instructions on how to get help and quit, and
other stuff.]
? 2+2
%1 = 4
i.e. have an informative banner, but have a command line option to suppress it.
John
2009/8/22 Simon King :
>
> On 22 Au
Hi,
Before this thread gets out of hand, note that this is a canonical example
of "Painting the Bike Shed". Please see
http://www.unixguide.net/freebsd/faq/16.19.shtml
if you don't know what I'm talking about.With that remark made, I do
think redesigning the banner is a great
On 22 Aug., 10:41, Simon King wrote:
> 4.
> sage_help(foo), where "foo" is any object, prints (or shows in
> "less"):
> 'Note: Typing "%s??" will give you the following information more
> easily.\n\n%s'%(foo.__name__, foo.__doc__)
I meant to only write 'Note: Typing "%s?" will...', not ??.
Sorry
Hi John,
On 22 Aug., 08:03, John H Palmieri wrote:
> * Type "notebook()" for the notebook interface.
+1 for mentioning the notebook, but I think 'type "notebook()" for the
GUI' is shorter, and since the word "notebook" is an explicit command
name, it is quite likely that the user understands wh
On Aug 21, 11:03 pm, John H Palmieri wrote:
> Okay, so what information do we need to include in the banner? I
> suggest we vote on each item, and then worry about how to word each
> item and how to assemble all of the results. I'll post suggestions,
> and then I'll vote myself in a separate me
Okay, so what information do we need to include in the banner? I
suggest we vote on each item, and then worry about how to word each
item and how to assemble all of the results. I'll post suggestions,
and then I'll vote myself in a separate message.
* Type "notebook()" for the notebook interfac
John H Palmieri wrote:
> Here's a proposal: the banner could look like this (looks best in
> fixed-width font -- the first line and the last two lines are
> centered):
>
> --
> |Sage version 4.1.1, release date 2009-0
On Aug 21, 2009, at 6:02 PM, Nick Alexander wrote:
> On 21-Aug-09, at 4:00 PM, John H Palmieri wrote:
>
>>
>> Here's a proposal: the banner could look like this (looks best in
>> fixed-width font -- the first line and the last two lines are
>> centered):
>>
>>
On 21-Aug-09, at 4:00 PM, John H Palmieri wrote:
>
> Here's a proposal: the banner could look like this (looks best in
> fixed-width font -- the first line and the last two lines are
> centered):
>
> --
> |Sage versi
Here's a proposal: the banner could look like this (looks best in
fixed-width font -- the first line and the last two lines are
centered):
--
|Sage version 4.1.1, release date 2009-08-14 |
|
On Fri, Aug 21, 2009 at 11:24 AM, Harald Schilly
wrote:
>
> On Aug 21, 7:12 pm, Simon King wrote:
> > return a
> > dictionary D, where..
>
> I like that idea!
> Let's start with collecting commands:
>
> import sys; sys.platform for the platform?
>
> os.environ['SAGE_ROOT'] might be nice for bugre
On Aug 21, 7:12 pm, Simon King wrote:
> return a
> dictionary D, where..
I like that idea!
Let's start with collecting commands:
import sys; sys.platform for the platform?
os.environ['SAGE_ROOT'] might be nice for bugreports?
import multiprocessing; multiprocessing.cpu_count()
for cpu count,
2009/8/21 Simon King :
> However, I am not so sure if I want to see all technical data when
> starting sage. Imagine how this would look on sage.math -- would it
> list all 24 processors?
>
> Cheers,
> Simon
I don't see anything wrong with '24 CPUs'
I feel if people use a remote system, it is
On Fri, Aug 21, 2009 at 8:37 AM, John H Palmieri wrote:
>
> On Aug 21, 8:17 am, Craig Citro wrote:
> > > Perhaps a function "get_help()" (or "help()") could print a link to
> > > sage-support, could print the needed technical data, *and* could print
> > > a brief introduction on how to post a goo
Hi David,
On Aug 21, 5:54 pm, David Kirkby wrote:
> 2009/8/21 Simon King :
[...]
> I don't see anything wrong with '24 CPUs'
Sure, '24 CPUs' is short enough. But by "listing all 24 CPUs", I mean
something like the output of "cat /proc/cpuinfo", which really is
quite long.
I am +1 concerning a
On Fri, 21 Aug 2009, Dr. David Kirkby wrote:
>
> When Sage starts, it gives you the version and license, but not much else.
>
> --
> | Sage Version 4.1.1, Release Date: 2009-08-14 |
> | Type notebook() for t
On Aug 21, 8:17 am, Craig Citro wrote:
> > Perhaps a function "get_help()" (or "help()") could print a link to
> > sage-support, could print the needed technical data, *and* could print
> > a brief introduction on how to post a good request (i.e., odds are
> > that we understand what the user mea
> Perhaps a function "get_help()" (or "help()") could print a link to
> sage-support, could print the needed technical data, *and* could print
> a brief introduction on how to post a good request (i.e., odds are
> that we understand what the user means):
>
I much prefer something along these line
Hi!
On Aug 21, 12:13 pm, David Joyner wrote:
> I don't object much but I wonder if variable output should always
> be tested and I don't know how to test the banner display. If this is
> not voted for, I would like to see this as an option to the "version"
> command.
It is indeed not nice if th
On Fri, Aug 21, 2009 at 5:04 AM, Dr. David
Kirkby wrote:
>
> When Sage starts, it gives you the version and license, but not much else.
>
> --
> | Sage Version 4.1.1, Release Date: 2009-08-14 |
> | Type noteb
22 matches
Mail list logo
