-
Notifications
You must be signed in to change notification settings - Fork 329
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
Feature request: Add file permissions and owner to "info" option #1554
Comments
I have prepared changes to support this, let me know if the project is interested in having it implemented and I will open a PR. |
Hi, I think permission should be straightforward to implement. But for user/group, this is a bit tricky because if there are different values then it could cause the fields to not align properly. In your example, it works conveniently because the value is always
|
That's a good point I hadn't considered, I'll see if I can come up with something. |
Also I took a very quick look at your fork, you should make documentation changes to |
Fixed, thanks. Once solution to the width issue I could think of is to calculate the maximum of user/group before iterating Using a forced width of ~8 is cleaner to implement but less flexible. I've added the aforementioned approach but I would understand if you prefer using a constant width. I think most people use short names most of the time, anyway. |
OK, I forgot about the possibility of just doing a second pass to obtain the max user/group widths - that should work too and is probably better than using a hardcoded width. I think this feature is worth including - if you submit it as a PR I will review it in more detail. |
Allow setting permissions (mode) and user/group owner to the
info
option, similar to what is possible inpromptfmt
.As an example to illustrate what I'm requesting, imagine this was set in
lfrc
:Which would then give:

The text was updated successfully, but these errors were encountered: