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
The file on disk has changed #2531
Comments
Same problem with realtime. ❯ findmnt /home
TARGET SOURCE FSTYPE OPTIONS
/home /dev/mapper/cryptroot[/@home] btrfs rw,relatime,ssd,discard=async,space_cache=v2,commit=600,sub
~
❯ stat ~/.config/micro/settings.json
File: /home/sergey/.config/micro/settings.json
Size: 331 Blocks: 8 IO Block: 4096 regular file
Device: 0,40 Inode: 7800329 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ sergey) Gid: ( 1000/ sergey)
Access: 2022-08-21 21:51:23.978554911 +0300
Modify: 2022-08-21 21:51:27.441836219 +0300
Change: 2022-08-21 21:51:27.441836219 +0300
Birth: 2022-08-21 21:20:29.664083643 +0300
~
❯ cat ~/.config/micro/settings.json
{
"colorcolumn": 80,
"ft:go": {
"tabstospaces": false
},
"ft:python": {
"colorcolumn": 78,
"tabsize": 4
},
"ftoptions": false,
"lsp.server": "python=pylsp,go=gopls,typescript=deno lsp",
"rmtrailingws": true,
"softwrap": true,
"tabsize": 2,
"tabstospaces": true
}
~
❯ stat ~/.config/micro/settings.json
File: /home/sergey/.config/micro/settings.json
Size: 331 Blocks: 8 IO Block: 4096 regular file
Device: 0,40 Inode: 7800329 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ sergey) Gid: ( 1000/ sergey)
Access: 2022-08-21 21:53:27.619185690 +0300
Modify: 2022-08-21 21:51:27.441836219 +0300
Change: 2022-08-21 21:51:27.441836219 +0300
Birth: 2022-08-21 21:20:29.664083643 +0300
~
❯ micro ~/.config/micro/settings.json
Found existing alias for "micro". You should use: "nano" |
Fixed by #3009 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When i open
~/.config/micro/settings.json
I always see promptThe file on disk has changed
.My
/etc/fstab
:Does micro require
atime/realtime
insteadnoatime
??????????????????The text was updated successfully, but these errors were encountered: