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.

Sign up for GitHub

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

Jump to bottom

Can't perform a real warm start which empties call stack but leaves dictionary intact #9

Open
Bushmills opened this issue Jan 20, 2022 · 1 comment
Open

Can't perform a real warm start which empties call stack but leaves dictionary intact #9

Bushmills opened this issue Jan 20, 2022 · 1 comment

Comments

@Bushmills
Copy link
Owner

Therefore will errors and breaks (Ctrl-C) pile up new quit instances on top of those which got interrupted or error trapped.
Response of yoda to Ctrl-C can be set as preference in yoda.conv. This setting exists because of not having a clean warm start.
Current workaround: don't push Ctrl-C thousands of times.

Second best thing which I can currently do is a cold start instead, which will also reset dictionary to boot conditions (empty it, that is).
Not exactly the kind of response you wish to happen for a simple "word not found" typo.
@Bushmills
Copy link
Owner Author

status line show now the number of functions on call stack, which increases with each caught error or Ctrl-C. That number can be used to determine when the right time to exit and restart yoda may have arrived.
I usually don't let it grow beyond a low three digit number.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Bushmills