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

Option to disable retro console effect #3067

Closed
zsunberg opened this issue Oct 18, 2024 · 2 comments
Closed

Option to disable retro console effect #3067

zsunberg opened this issue Oct 18, 2024 · 2 comments

Comments

@zsunberg
Copy link

zsunberg commented Oct 18, 2024

Would it be possible to add an option to disable the retro console effect for printed text? By "retro console effect", I mean the lighter and darker lines in this image that move slowly downward.

image

My interpretation is that someone added this to discourage use of print statements by making it seem more old-fashioned and clunky. I understand this, and it is fine to have it on by default, but this degrades the user experience by being very distracting when you do have to deal with printed output. Can we get an option to turn it off when we do need to examine printed output? 🙂

@fonsp
Copy link
Owner

fonsp commented Oct 21, 2024

Hi @zsunberg !

There are always good alternatives to print statements, and Pluto's design should encourage that :) There won't be an option to turn of the visual effect, but there are many options to improve your code!

The easy alternative is to use @info(...) instead of print.

In your case, since your are displaying a table, you can create a table with DataFrames or similar, and output it in the cell. (You can also log it with @info to display the table during computation.)

If your goal is to display grid-formatted text, then check out the Julia Text function. If your Pluto cell returns a Text object, the string will be formatted monospace with original whitespace (without a retro effect).

@fonsp fonsp closed this as not planned Won't fix, can't repro, duplicate, stale Oct 21, 2024
@zsunberg
Copy link
Author

I see, I didn't know that the logging functions like @info display differently. Thanks for the clarification.

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

No branches or pull requests

2 participants