-
Notifications
You must be signed in to change notification settings - Fork 19
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
Questions about the polymake shell mode #426
Comments
This is supposed to mimic the normal polymake shell as closely as possible. Automatically printing objects can have some unintended side-effects in perl, e.g. visualization windows opening twice, because the to-string operator might be overloaded. So I would prefer not to change this.
This seems to be undocumented, but we can add a short description for this prompt in a few places.
Yes, that should be easy to add. (I recently noticed that the
It is again replicating the normal polymake prompt and But it might make sense to add |
+1 from me for |
I recently discovered the polymake shell mode trigger by
$
pressed at the start of a Julia prompt, just like the Pkg and shell prompt modes in Julia. Nice!I have some questions / suggestions on this:
the prompt does not seem to echo results, unlike the Julia prompt. So if I do
$i = 42;
in one line; and then on the next line enter$i;
, I would expect it to print 42 but it does not. I figured out that I can doprint($i);
to see it, but I think it would be nice to get this echo. Would this be possible to add?Is there any documentation? Or a desire at least for some? I'd be happy to contribute, too.
Could we also make it accessible via say
Polymake.prompt()
to make it more discoverable? Just like we haveGAP.prompt()
(in return, I also would like to be able to trigger the GAP prompt with a key press, but it has problems, like: not being discoverable; unclear what to do if other packages use the same hotkey; difficult to visually show what happens when entering/exiting the mode in demos)Why is the prompt
common >
(with a space) and notcommon>
or evenpolymake>
?The text was updated successfully, but these errors were encountered: