-
Notifications
You must be signed in to change notification settings - Fork 96
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 keep output style #78
Comments
I agree, this might be a useful option. Perhaps here? https://github.com/kynan/nbstripout/blob/master/nbstripout.py#L184 |
Agreed, that'd be a welcome addition. Do you feel like working on a pull request @melsophos @jeremydouglass ? |
Is this still a use case you have @melsophos @jeremydouglass ? |
I have not used much notebooks in the last year. As a matter of principle, I think that the option is still useful, but I don't have a strong motivation for it now. |
@kynan - Unfortunately I haven't been using notebook-based projects much recently, so I don't have an active use case to test this right now. |
@kynan I can work on this since I need it. |
with `nbstripout --keep-metadata-keys` or git config key `filter.nbstripout.keepmetadatakeys`. closes kynan#78
with `nbstripout --keep-metadata-keys` or git config key `filter.nbstripout.keepmetadatakeys`. closes kynan#78
with `nbstripout --keep-metadata-keys` or git config key `filter.nbstripout.keepmetadatakeys`. closes kynan#78
with `nbstripout --keep-metadata-keys` or git config key `filter.nbstripout.keepmetadatakeys`. closes kynan#78
with `nbstripout --keep-metadata-keys` or git config key `filter.nbstripout.keepmetadatakeys`. closes kynan#78
with `nbstripout --keep-metadata-keys` or git config key `filter.nbstripout.keepmetadatakeys`. closes #78
It would be nice to have an option to keep the way output is displayed (between standard, scrolled, and collapsed) since it is more part of formatting than of outputs (I am enabling scrolling when I know that the output will be large, but when I still want to display it).
The text was updated successfully, but these errors were encountered: