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

Can't edit settings.json #3484

Open
tsilvs opened this issue Sep 27, 2024 · 4 comments
Open

Can't edit settings.json #3484

tsilvs opened this issue Sep 27, 2024 · 4 comments

Comments

@tsilvs
Copy link

tsilvs commented Sep 27, 2024

Description of the problem or steps to reproduce

Every time I'm editing & saving ~/.config/micro/settings.json it is being reset by something. And the editor prompts with The file on the disk has changed.. Permissions are correct. Ownership is correct. Doing this as the owner. Nothing is using the file, according to sudo fuser ~/.config/micro/settings.json.

Specifications

  • OS: Bazzite Holographic 40 (Silverblue) x86_64
  • Terminal: Ptyxis 46.6
  • Commit hash: 225927b
@Andriamanitra
Copy link
Contributor

Andriamanitra commented Sep 27, 2024

Micro does some slightly annoying auto-formatting on the file whenever settings are changed (with the set command or config.SetGlobalOption in Lua) even if the new value for the option is the same as the existing one. You might have have some plugin that is programmatically changing an option.

You can disable "The file on the disk has changed" prompt by setting set reload auto.

@dmaluka
Copy link
Collaborator

dmaluka commented Sep 27, 2024

Also 225927b is 2.0.11 i.e. a pretty old version of micro. Since 2.0.14 we have the fix #3009 which avoids unexpected rewriting of settings.json in most cases.

@tsilvs
Copy link
Author

tsilvs commented Sep 28, 2024

a pretty old version of micro

I am currently using micro from Fedora repo. Will contact maintainers to ask them to update it.

@JoeKar
Copy link
Collaborator

JoeKar commented Sep 30, 2024

I am currently using micro from Fedora repo. Will contact maintainers to ask them to update it.

Hm, right...pretty old, what they package right now. Even debian offers a newer package from testing onwards.
Anyway, there is already the "bug" reported/identified by the upstream release monitor (2238002) of Fedora, while for Debian it is 1080422.
Nevertheless you can use our generic and static artifact for v2.0.14 (micro-2.0.14-linux64-static.tar.gz + micro-2.0.14-linux64-static.tar.gz.sha) as long as it isn't available as package in your favorite distribution.

We should be ready to close this issue, am I right?

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

4 participants