Skip to content
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

Some way to keep or retrieve evaluation strings #123

Open
martinmcclure opened this issue Nov 18, 2022 · 1 comment
Open

Some way to keep or retrieve evaluation strings #123

martinmcclure opened this issue Nov 18, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@martinmcclure
Copy link
Member

Under some circumstances, it would be nice to be able to keep the contents of evaluator sub-panes, or to retrieve the contents of recently closed ones.

For instance, this sequence is fairly common:

  • Evaluate expression 1 in an inspector pane, resulting in object A.
  • Evaluate a expression 2 in the inspector pane for object A.
  • Edit expression 1 to form expression 1a, and evaluate that, resulting in object B.
  • Evaluate expression 2 in the inspector pane for object B.

This is currently awkward, because evaluating expression 1a replaces the inspector pane for A with that for B, closing any evaluators you had in that pane. Might be nice to keep them by default?

The fix for #111 would help in slightly different cases, especially when inspecting temporary variables in a debugger frame, and stepping.

Having a viewable history of recently-used evaluations would also be good, as well as a way to save a library of commonly-used expressions.

@martinmcclure martinmcclure added the enhancement New feature or request label Nov 18, 2022
@martinmcclure martinmcclure self-assigned this Nov 18, 2022
Copy link
Member

a "do it" log file. external, so one can't lose them accidentally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants