-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
effects of GAP's Browse on Julia's screen output? #741
Comments
A wild guess: julia seems to implement its own Ctrl-Z handling (see |
From the
I am pretty sure this interferes with Julia, which also kinda wants to control the screen... Now, we could certainly perform some tricks to deal with this (e.g. set up a temporary SIGTSTP handlers before calling |
It seems that pressing ctrl-z while Browse is active is somewhat broken even in regular GAP. E.g. when I enter |
I think we have to distinguish three different situations:
Concerning the example mentioned above: |
The same behaviour occurs when using OSCAR without any other packages. |
On Sun, Mar 10, 2024 at 01:15:15AM -0800, Erik Paemurru wrote:
> When I suspend the Julia session with Ctrl-Z and then enter the session again, the terminal gets cleared
The same behaviour occurs when using OSCAR without any other packages.
polymake and Gap play with signal handlers?
… --
Reply to this email directly or view it on GitHub:
#741 (comment)
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
The browse package is unconditionally calling |
I am using Julia 1.6.3 with the develop version of GAP.jl.
The GAP package Browse has been installed via `GAP.Packages.load("Browse", install = true).
When I suspend the Julia session with Ctrl-Z and then enter the session again, the terminal gets cleared, the Julia prompt appears in the first line, and afterwards the distribution of Julia's output to lines does not fit anymore.
This problem disappears as soon as I deinstall the Browse package.
(This problem is sort of a continuation of #456, but since the effects are different, I opened a new issue instead of reopening #456.)
The text was updated successfully, but these errors were encountered: