micro-editor / micro-editor/micro

Micro do not save file and reopen old file

Open
#3,096 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
29.6k
Forks
1.4k
Avg merge
2d 18h
Merged PRs (30d)
10

Description

Linux desktop Zorin Pro 16.3

Micro is not saving file and when opening the same file, after closing and reopening it with micro give the msg

The file on disk has changed. Reload file (y,n,esc)

Closing micro, starting vim, deleting a line with vim for testing...cat file to verify

Micro is loading the old file again (from WHERE ???) deleting a line with micro, saving the file C-s, C-q restart micro file IS NOT updated (Did a check by using vim).

Package from Zorin distribution. Did install a snap version, same result.

Standard installation at ~/.config/micro

Apparently it is happening with the configuration files (in this case bindings.json)

NO automatic saving

Screenshot from 2023-12-15 12-14-38

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the save, close, and reopen sequence on Linux, then compare the file with vim or cat as described. Inspect the standard ~/.config/micro setup, especially bindings.json, and use the reload warning to narrow the behavior. Done means the cause is identified and a reproduction confirms that C-s/C-q persists changes and reopening no longer restores old content.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.