FWIW, I just submitted a pull request against sage-shell-mode to fix this
issue (by reverting to readline and using --simple-prompt).
A better solution (manage CPR requests in emacs) is out of my abilities...
Le mardi 11 août 2020 à 18:54:30 UTC+2, John H Palmieri a écrit :
> Done. I haven't
Yes, using "sage —simple-prompt“ did fix the problem as well. However, the
simple prompt lacks a lot of functionality, like cursor movement,
tab-completion or colors. I assume that Emacs is more advanced and implements
these features by different means, but for Vim this is not really an option.
On Friday, August 21, 2020 at 1:37:21 PM UTC-7, Markus Wageringel wrote:
>
> With Neovim as editor, the same warning appears in its builtin terminal,
> followed by some error messages that break the REPL. Luckily, upgrading
> Neovim from 0.2.2 to 0.4.3 fixed it on my end.
>
Does
With Neovim as editor, the same warning appears in its builtin terminal,
followed by some error messages that break the REPL. Luckily, upgrading
Neovim from 0.2.2 to 0.4.3 fixed it on my end.
emanuel.c...@gmail.com schrieb am Dienstag, 11. August 2020 um 17:39:29
UTC+2:
> Damn !
>
> This
Running tests with few optional and external packages (but not internet due
to some issue with my current installation), I get
Using
2020-08-13 21:59:31 UTC, Dima Pasechnik:
>
> OK, I tried to reproduce this on a Mac, and indeed the build hangs
> waiting for some parallel process to finish:
> On hitting ctrl-C, it always (the stage of the docbuild may differ though)
> shows the following backtrace:
> ...
> [dochtml]
OK, I tried to reproduce this on a Mac, and indeed the build hangs
waiting for some parallel process to finish:
On hitting ctrl-C, it always (the stage of the docbuild may differ though)
shows the following backtrace:
...
[dochtml] [a_tour_of] dumping search index in English (code: en)... done
On Thursday, August 13, 2020 at 12:24:05 PM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Thu, 13 Aug 2020, 20:03 John H Palmieri, > wrote:
>
>>
>>
>> On Thursday, August 13, 2020 at 11:44:59 AM UTC-7, Samuel Lelievre wrote:
>>>
>>> I opened a ticket for the issue reported by John:
>>>
>>> - Fix
On Thu, 13 Aug 2020, 20:03 John H Palmieri, wrote:
>
>
> On Thursday, August 13, 2020 at 11:44:59 AM UTC-7, Samuel Lelievre wrote:
>>
>> I opened a ticket for the issue reported by John:
>>
>> - Fix building html documentation on macOS
>> https://trac.sagemath.org/ticket/30351
>>
>> I tried
On Thursday, August 13, 2020 at 11:44:59 AM UTC-7, Samuel Lelievre wrote:
>
> I opened a ticket for the issue reported by John:
>
> - Fix building html documentation on macOS
> https://trac.sagemath.org/ticket/30351
>
> I tried applying #30345 but the problem persisted.
> Then I realised Dima
I opened a ticket for the issue reported by John:
- Fix building html documentation on macOS
https://trac.sagemath.org/ticket/30351
I tried applying #30345 but the problem persisted.
Then I realised Dima mentioned #30345 in relation to
timeouts when running make testalllong on Debian,
not in
What happens if you do "make doc-clean; make"?
On Thursday, August 13, 2020 at 12:36:42 AM UTC-7, David Coudert wrote:
>
> on my side, incremental build from beta7 (including documentation) on OSX
> went well.
>
> Le 13 août 2020 à 07:35, John H Palmieri > a écrit :
>
> I'm having a problem
I'm using 10.15.6, 2017 iMac. Same thing with the system Python vs. Sage's
own. I have a bunch of homebrew packages installed, too.
On Thursday, August 13, 2020 at 1:55:44 AM UTC-7, Dima Pasechnik wrote:
>
> different versions of macOS?
>
> On Thu, Aug 13, 2020 at 8:36 AM David Coudert >
2020-08-13 05:35 UTC, John H Palmieri:
>
> I'm having a problem with this on OS X: both with an incremental
> upgrade (after doing "make doc-clean") and a build from scratch,
> the build hangs during the docbuilding stage.
Same here with this configuration:
- MacBook Air, Early 2014
- macOS
macOS Mojave 10.14.6
macbook air early 2014 with core i7 1.7GHz
> Le 13 août 2020 à 10:55, Dima Pasechnik a écrit :
>
> different versions of macOS?
>
> On Thu, Aug 13, 2020 at 8:36 AM David Coudert wrote:
>>
>> on my side, incremental build from beta7 (including documentation) on OSX
>>
different versions of macOS?
On Thu, Aug 13, 2020 at 8:36 AM David Coudert wrote:
>
> on my side, incremental build from beta7 (including documentation) on OSX
> went well.
>
> Le 13 août 2020 à 07:35, John H Palmieri a écrit :
>
> I'm having a problem with this on OS X: both with an
on my side, incremental build from beta7 (including documentation) on OSX went
well.
> Le 13 août 2020 à 07:35, John H Palmieri a écrit :
>
> I'm having a problem with this on OS X: both with an incremental upgrade
> (after doing "make doc-clean") and a build from scratch, the build hangs
>
I'm having a problem with this on OS X: both with an incremental upgrade
(after doing "make doc-clean") and a build from scratch, the build hangs
during the docbuilding stage. If I manually build "constructions" and
"thematic_tutorials" with "sage --docbuild constructions html" etc., the
build
On Wed, Aug 12, 2020 at 2:20 AM Matthias Köppe wrote:
>
> On Monday, August 10, 2020 at 3:51:35 PM UTC-7, Volker Braun wrote:
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>>
On Monday, August 10, 2020 at 3:51:35 PM UTC-7, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
>
> 415221a9a8 (trac/develop, tag:
On Tuesday, August 11, 2020 at 9:04:01 AM UTC-7, Emmanuel Charpentier wrote:
>
> I do not know how to re-open a closed ticket...
>
One doesn't.
I'd suggest to use https://trac.sagemath.org/ticket/25363 (simple-prompt)
for the things that need to be prepared on the sage side,
and
Done. I haven't figured out the sage-shell customizations so that it
automatically uses '--simple-prompt' whenever you ask it to start Sage, but
that's a separate problem.
On Tuesday, August 11, 2020 at 9:44:15 AM UTC-7, Emmanuel Charpentier wrote:
>
>
>
> Le mardi 11 août 2020 18:38:00 UTC+2,
Le mardi 11 août 2020 18:38:00 UTC+2, John H Palmieri a écrit :
>
> It's version 26.3. I also just quit emacs and restarted, and now I'm
> having the same problems you were having. Modifying 'src/bin/sage' to
> accept a '--simple-prompt'
>
How do you do that ? Care to post a diff (possibly
It's version 26.3. I also just quit emacs and restarted, and now I'm having
the same problems you were having. Modifying 'src/bin/sage' to accept a
'--simple-prompt' option and then using that seems to work.
On Tuesday, August 11, 2020 at 9:32:20 AM UTC-7, Emmanuel Charpentier wrote:
>
> John,
John, what is your current emacs version ?
Le mardi 11 août 2020 18:26:04 UTC+2, John H Palmieri a écrit :
>
> I had no experience with sage-shell-mode until about 5 minutes ago, but it
> works for me, except for some weird artifacts when it reprints what I typed
> at the command line:
>
>
I had no experience with sage-shell-mode until about 5 minutes ago, but it
works for me, except for some weird artifacts when it reprints what I typed
at the command line:
┌┐
│ SageMath version 9.2.beta8, Release Date:
Further bad news : this also somehow breaks the communication between emacs
and sage :
-
quit in the sage session never returns ; you have to kill emacs to get
your damn prompt back…
-
Any attempt to use sage from an org-mode document never returns : same
issue…
FWIW, i left a comment there pointing to the present thread. I do not know
how to re-open a closed ticket...
Le mardi 11 août 2020 17:54:37 UTC+2, Matthias Köppe a écrit :
>
> Yes, 9.2.beta8 did the overdue update from ipython 5 to 7 in
> https://trac.sagemath.org/ticket/28197
>
> On Tuesday,
Yes, 9.2.beta8 did the overdue update from ipython 5 to 7
in https://trac.sagemath.org/ticket/28197
On Tuesday, August 11, 2020 at 8:48:43 AM UTC-7, Dima Pasechnik wrote:
>
> it is probably a newer iPython that gives this, nothing Sage-specific it
> seems.
>
> On Tue, Aug 11, 2020 at 4:47 PM
The solution in that thread, using "--simple-prompt", is of course not
support by sage.
There's already a ticket for that: https://trac.sagemath.org/ticket/25363
which needs work
On Tuesday, August 11, 2020 at 8:47:00 AM UTC-7, Dima Pasechnik wrote:
>
> maybe,
>
>
it is probably a newer iPython that gives this, nothing Sage-specific it seems.
On Tue, Aug 11, 2020 at 4:47 PM Emmanuel Charpentier
wrote:
>
> I I filed [this issue](https://github.com/sagemath/sage-shell-mode/issues/53)
> against `sage-shell-mode` on Github.
>
> HTH,
>
> Le mardi 11 août 2020
I I filed [this issue](https://github.com/sagemath/sage-shell-mode/issues/53)
against `sage-shell-mode` on Github.
HTH,
Le mardi 11 août 2020 17:39:29 UTC+2, Emmanuel Charpentier a écrit :
>
> Damn !
>
> This release breaks sage-shell-mode support for a sage session into
> emacs. After
maybe,
https://stackoverflow.com/questions/60534394/ipython-warning-in-emacs-your-terminal-doesnt-support-cursor-position-requests
?
On Tue, Aug 11, 2020 at 4:39 PM Emmanuel Charpentier
wrote:
>
> Damn !
>
> This release breaks sage-shell-mode support for a sage session into emacs.
> After
Damn !
This release breaks sage-shell-mode support for a sage session into emacs.
After starting an emacs session, I get the normal banner and a normal
prompt. A little while after that (about 0.5 to 1 second), a warning WARNING:
your terminal doesn't support cursor position requests (CPR).
On Debian testing running on core i7 + 16 GB RAM, upgrading 9.2.beta7
configured for use of all possible system libraries an runningptestlong
gets me the same transient an same three permanent failures already
reported for 9.2.beta7 and 9.2.beta5 :
sage -t --long --warn-long 175.4
35 matches
Mail list logo
