Skip to content

Support semicolon (;) as a way to suppress output #3726

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

Closed
silky opened this issue Feb 8, 2025 · 0 comments · Fixed by #3830
Closed

Support semicolon (;) as a way to suppress output #3726

silky opened this issue Feb 8, 2025 · 0 comments · Fixed by #3830
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Your expertise is better than ours, we would love your help

Comments

@silky
Copy link

silky commented Feb 8, 2025

Description

In Jupyter, if you have a cell that ends in a function call with a semicolon, the output is supressed:

5

vs

5;

Image

In Marimo, this is not the case:

Image

The only way to achieve the same result is with a dummy assignment:

_ = 5

which is clearly unpleasant.

Suggested solution

Follow Jupyter and interpret the ; on the last statement as a indication that the output should be suppressed.

Alternative

No response

Additional context

This was on marimo 0.9.14

@silky silky added the enhancement New feature or request label Feb 8, 2025
@mscolnick mscolnick added good first issue Good for newcomers help wanted Your expertise is better than ours, we would love your help labels Feb 11, 2025
mscolnick pushed a commit that referenced this issue Feb 18, 2025
## 📝 Summary

Replaces #3806 

## 🔍 Description of Changes

Resolves #3726

@mscolnick

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Your expertise is better than ours, we would love your help
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants