-
Notifications
You must be signed in to change notification settings - Fork 348
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
view files in /proc #1475
Comments
Yazi uses yazi/yazi-config/preset/yazi.toml Lines 125 to 126 in 71d6b0d
If we want to support yazi/yazi-plugin/preset/plugins/file.lua Lines 3 to 5 in 71d6b0d
But I'm not sure if there's any way to do that. Any ideas? |
maybe implement some logic about the filesystem type its browsing would be good. if its proc it could just display the text of filenames without extensions (ie: not this would also solve another issue i have on |
I'm not sure I understand you correctly - do you mean that
Are you saying to use the filename as the preview content on the right pane? |
it is a virtual filesystem of type > grep proc /proc/mounts
proc /proc proc rw,nosuid,nodev,noexec,noatime 0 0
Sorry, no. In |
Does this mean that all Unix-like systems have a I noticed that there are some directories in |
on linux the maybe there is an OS independent rust crate that does all this.
I see. those files have size > 0. the 'lf' file browser shows them as binary. maybe if it's a regular file and 0 size, just cat it, if it has size, run file on it. |
It looks like macOS doesn't implement |
Please try #1482 |
works great! Thanks! |
I'm going to lock this issue because it has been closed for 30 days. ⏳ |
yazi --debug
outputPlease describe the problem you're trying to solve
when browsin /proc I'd like to be able to preview the contents of the virtual files.
currently yazi shows them as empty
for example lf displays their content in preview.
Would you be willing to contribute this feature?
Describe the solution you'd like
id like to see the contents of the file
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: