On Thu, Aug 16, 2018 at 2:50 PM Jeroen Demeyer wrote:
>
> On 2018-08-16 14:30, Erik Bray wrote:
> > In the meantime I think we should remove that warning, or at least
> > have a way to disable it, as it's clearly confusing to users.
>
> *NOT* having the warning is also confusing to users (that's
On 2018-08-16 14:30, Erik Bray wrote:
In the meantime I think we should remove that warning, or at least
have a way to disable it, as it's clearly confusing to users.
*NOT* having the warning is also confusing to users (that's why it was
added in the first place). So if the warning is not
On Wed, Aug 15, 2018 at 11:08 AM Jeroen Demeyer wrote:
>
> On 2018-08-14 23:43, Erik Bray wrote:
> > Isn't that just the normal message when running `sage -sh`?
>
> IIRC, I added that text because people were generally quite confused
> which kind of commands should be run inside or outside of a
On 2018-08-14 23:43, Erik Bray wrote:
Isn't that just the normal message when running `sage -sh`?
IIRC, I added that text because people were generally quite confused
which kind of commands should be run inside or outside of a Sage shell.
The top-level "make" commands are typically run
On 8/14/18 5:43 PM, Erik Bray wrote:
Isn't that just the normal message when running `sage -sh`?
Indeed! I thought it was some cygwin special but it is in
$SAGE_ROOT/src/bin/sage at lines 735-742.
I never even read it that closely. Why *does* it say that? I install
packages and run make from
Isn't that just the normal message when running `sage -sh`?
I never even read it that closely. Why *does* it say that? I install
packages and run make from within the sage subshell all the time.
Especially when it comes to optional packages (which should maybe be the
only kind actually supported
Dear all (I guess mostly Erik),
When a sage shell is launched on windows (ie the sage -sh environment in
cygwin) the following message is displayed
"""
Starting subshell with Sage environment variables set. Don't forget
to exit when you are done. Beware:
* Do not do anything with other
