marimo-team
Configurable auto-export location
Description
Right now auto-export to HTML places its outputs in a .marimo directory. I would like to be able to save it as a sibling file instead. :)
Suggested solution
Alternative
No response
Additional context
No response
Thanks for the suggestion. I think a sibling file is a good default option -- notebook.py and notebook.html. Since the user is probably checking in the html to their git rep (even if they're not looking at diffs, just as an artifact).
I'd be open to just making that the default behavior, instead of adding config, but curious what @mscolnick thinks.
@patrick-kidger - the reason i made it .marimo was so that it is easier to .gitignore, especially if we add more auto-export types (markdown, etc).
also i felt the .marimo was cleaner to house more cache/outputs that we may have in future
Honestly I see the argument both ways. Sometimes I may wish to check that in; sometimes I may prefer not to (and putting it in .marimo is an easy .gitignore target).
Haha, jinx. So anyway, I'm not going to advocate for a change of default, just the ability to keep it out of .marimo if I want to.
(I appreciate every extra configurable option is a step closer to a kitchen-sink UX nightmare)
Yea, I agree leaving .marimo as the default. I think this makes sense as user-config (well, really, project config) so you don't need to do this for each marimo file in your project. Open to suggestions though.
I think we can support this, I may not get to it for a bit. (maybe in the meantime could have a pre-commit that moves it up a folder)
FWIW, at least right now I'd like to be able to control this on a per-file basis, not a per-user basis.
@patrick-kidger, fyi, still not configurable, but it got moved from .marimo to __marimo__ (https://github.com/marimo-team/marimo/pull/2468)