Can't trace config file when overwritten by pyproject.toml

[KennethEnevoldsen]

So I am fairly new to Marimo so this might be an error on my end.

I have the following issue: I want autosave turned on but get a warning stating that it is overwritten:

First, I tried just deleting pyproject.toml file in the git repo. This did not change anything.
Then I tried adding the following to the pyproject.toml

...

[marimo.tool.save]
autosave_delay = 1000
format_on_save = true
autosave = "after_delay"

this did not change the problem either.

Then I went out a folder and create a new notebook (assuming that it might look further down my directory):

cd ..
mkdir tmp
cd tmp
marimo new

Here, I did not have the issue.

This leaves me with a problem and a 'confusion':

• problem: I can't figure out where the pyproject.toml is located.
• confusion: Having newer specified marimo in a pyproject.toml before I do not understand why it would overwrite my settings

If I run marimo config show then I get:

...

[save]
autosave_delay = 1000
format_on_save = true
autosave = "after_delay"

...

A simple solution might be to allow me to click the pyproject.toml to go to the file or see the path.

[mscolnick]

If you do marimo config show, it should show you the pyproject.toml it is pulling in. Can you paste your full output (and hide any sensitive info)?

Also your configuration in pyproject.toml should be: [tool.marimo.save], not [marimo.tool.save], following the best practices for pyproject.toml config

[mscolnick]

@KennethEnevoldsen , i might have figured it out. Is it because you are running with --watch?

This wording is incorrect - it's not overridden by pyproject.toml, but it is overridden because auto-saving is disabled while in watch mode. (otherwise it will get conflicts with your external editor)

[bulletmark]

I just had this problem. Spent a while then came to raise a bug and found this bug and #4196 which told me it was due to me running with --watch. I have been doing that lazily every time just in case I want to directly edit but seems there is a disadvantage to doing that.

[KennethEnevoldsen]

I am running it using the VS code extension which indeed does run it using --watch:

/Users/au561649/Github/danish-dynaword/.venv/bin/python -m marimo --yes edit /Users/au561649/Github/danish-dynaword --host=localhost --port=2818 --headless --no-tok
en --watch

I must say I wasn't expecting that behavior. I can see why: you are expecting me to edit the code files and use the marimo notebook as a "viewer".

[mscolnick]

Yes, the intention is to avoid auto-writes from 2 editors which could lead to loss of data. If people feel strongly they want autosave to still exist in --watch, then we can look into it (and make sure it is hardened / wont lead to data corruption).

As an example, we use test runners with snapshotting which changes the file externally as I write in it. Very often I hit a case there my vscode editor is out of date and either I have to overwrite the file and handle merge conflicts, which is a very poor experience.

[bulletmark]

When I discovered here that the reason autosave was disabled was because I was using --watch I thought that completely reasonable. Trying to autosave in parallel to an external editor seems fraught with danger. Simply, the bug here that needs fixing is that when using --watch the user settings page says that the "autosave state is overwritten by pyproject.toml" which is wrong and very confusing.

[mscolnick]

I agree, @bulletmark, it is confusing messaging / we can fix that.

[KennethEnevoldsen]

Yeah, updating the message is a strong first step here.

Yes, the intention is to avoid auto-writes from 2 editors which could lead to loss of data. If people feel strongly they want autosave to still exist in --watch, then we can look into it (and make sure it is hardened / wont lead to data corruption).

And the two editors would be browser and VS code? Or VS Code Marimo view and code view?

As I see it now, there seems two intended ways to code with Marimo in notebooks:

• split screen notebook / marimo
• split screen script / marimo

I was kinda expecting a mode running just "marimo". I can create this using "marimo.watch": False and just closing one view notebook/script view.

(After having experienced all three, I understand the two first and probably prefer them, but as a new user, I was expecting option 3)