-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
read only indicator #3709
read only indicator #3709
Conversation
Do we want read-only indicators in bufferline as well? It's an easy add. |
// this seems overly complex but should make it easier | ||
// to extend doc.file_stat with more information in the future. | ||
doc.write_permission = fs::metadata(path).map_or(WritePermission::Unknown, |f| { | ||
if f.permissions().readonly() { | ||
WritePermission::ReadOnly | ||
} else { | ||
WritePermission::Writable | ||
} | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably be part of doc.set_path
since a path can also be changed after opening?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the implications of changing a path after opening?
Why did the author close this without any info? |
Does anyone know if there's work ongoing for a read-only indicator, or a read-only flag/option for buffers? I can't find any info about why this PR was closed or anything happening after it. |
Rebased #2862.