-
Notifications
You must be signed in to change notification settings - Fork 160
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
Restoring saved workspaces broken in GAP 4.12? #5014
Comments
Just for confirmation, I assume you downloaded the tarball from www.gap-system.org? |
Yes, and this gave me https://github.com/gap-system/gap/releases/download/v4.12.0/gap-4.12.0.tar.gz |
It would be good some more details -- I tried reproducing this but it seemed to work fine (I'm on Ubuntu in WSL). A full terminal cut, like this, would be helpful if yours is different:
|
Aaaah, the way I am calling GAP in a script seems to disable readline:
I checked an old workspace, there readline support was not disabled by this way of calling GAP. Do you have a suggestion on how to call GAP with multiline input from a script and keep readline support enabled? (I tried the In any case, thanks for the super fast reply and sorry for the false alarm! |
In terms of fixing your issue, you could replace running GAP with something like this:
However, leave this issue open for now, as I'm interested why this used to work, and now doesn't, particularly if (based on @frankluebeck 's name), this is a script multiple people might be using. |
Having looked through history, this is caused by |
I will update the |
I agree that it is sensible to disable readline by default when GAP's input is not a terminal. But why does GAP ignore an explicit For the rsync distribution I have now changed the script that generates the workspace (the script does no longer redirect the standard input but just reads a file): see this commit |
One minor point, actually If people want this, and want something less confusing, we could easily add |
This is a general concern I have with the GAP command line options: a lot of them toggle behavior, which can make it difficult to reliable ensure things are really turned on or off (think of |
Indeed, toggling options are only useful when the default is fixed (which was the case in "old" GAP versions). |
So, how do we want to deal with this? For E.g. first we use a patch like this:
Next, when restoring savespaces, we ignore the actual As an alternative to the second part, we could change the code in |
My concern (and it's hard to know without tracing the code) is if this will reintroduce the bugs we were fixing by adding this -- there are some separate things, did we build with readline, and are we actually using it, and the question is will GAP misbehave if, when we load in the saved workspace, we start using readline when we weren't before? |
Punting to 4.12.2 as nobody worked on a fix. |
Now that I managed to create the workspace using the workaround suggested by Frank the history saving does not work. |
Nobody has voiced intention to work on this, and so it won't be fixed in 4.12.2, and realistically not in any 4.12.x. I am going to punt it to the 4.13 milestone, but that won't fix it magically either, it'll just ensure it'll be revisited by me before that release.... We'll see what happens |
... by reverting a previous change that made us disable readline when stdin is not connected to a terminal (see gap-system#4495). While that still seems useful, and avoids certain issues when piping GAP output into files, it needs a better implication that avoids the issues described in gap-system#5014 Also add a separate CI test suite target "testworkspace" for testing for this issue, and potentially other workspace related issues.
... by reverting a previous change that made us disable readline when stdin is not connected to a terminal (see gap-system#4495). While that still seems useful, and avoids certain issues when piping GAP output into files, it needs a better implication that avoids the issues described in gap-system#5014 Also add a separate CI test suite target "testworkspace" for testing for this issue, and potentially other workspace related issues.
... by reverting a previous change that made us disable readline when stdin is not connected to a terminal (see #4495). While that still seems useful, and avoids certain issues when piping GAP output into files, it needs a better implication that avoids the issues described in #5014 Also add a separate CI test suite target "testworkspace" for testing for this issue, and potentially other workspace related issues.
When creating a workspace and trying to load it with GAP 4.12, the following error occurs:
For me this looks like the version number is not handled consistently (once with "with readline" and once without). If you cannot reproduce, I will of course provide more details.
The text was updated successfully, but these errors were encountered: