-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
feat: Plugin support #991
Comments
Not sure how relevant it is to mention a completely different tool in this repo, but you might like nushell. For example, I just wrote this little command that adds a line count to every file from ls (it generates some warnings, but that's fixable):
It's fairly easy to define a new command It serves a bit of a different purpose from eza, but if you need a tool where you want |
Another option may be to one day support nushell "natively", so we can get nice columns and stuff when run in nushell, I think @PThorpe92 looked at it at some point, but IIRC it would require a lot of work. I do know there exists some snippet in the nushell discord for converting eza output to something nushell understands FWIW. |
It would be nicer to offload this to the shell rather than us having to maintain a plugin system, also from like an ecosystem perspective, it seems more reasonable to have some universal language rather than over-specializing every single binary. |
OK, maybe this is a wishful thinking which is waaaaaay out of what eza is supposed to do. But let me dream ....
Somehow, a plugin configuration is provided to eza that consists of these parts:
Many plugins can be defined as above at the same time, as long as their names do not clash.
If user calls eza with short or long option name as defined above, then for each file system object eza calls the executable above, and prints the returned values in the appropriate column.
Now, obviously using plugins could take a performance hit, and users must be aware of it. But eza must try and minimize it:
max-threads
?The text was updated successfully, but these errors were encountered: