You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In conjure, all your evaluation goes to a log buffer, it contains the evaluated code, the output, along with stdout. User is free to modify anything in that buffer and it won't be stored as it's a temporary buffer.
This will be really helpful for users to tinker around with their code without being afraid that their codebase is broken.
The text was updated successfully, but these errors were encountered:
Hello, if I implement this feature would you like to accept it @liquidz ? :)
It depends on the policy of implementation.
vim-iced already has a Stdout buffer, and I want to avoid a situation where multiple similar features exist.
So, the policy should either completely replace the Stdout buffer, or extend the Stdout buffer.
But, it is currently possible to output evaluation code and evaluation results to the Stdout buffer using the Hook feature,
so if the policy is to extend the Stdout buffer, we also need to consider conflicts with the Hook feature.
In conjure, all your evaluation goes to a log buffer, it contains the evaluated code, the output, along with stdout. User is free to modify anything in that buffer and it won't be stored as it's a temporary buffer.
This will be really helpful for users to tinker around with their code without being afraid that their codebase is broken.
The text was updated successfully, but these errors were encountered: