When running open file in bash, it opens in a default local app.
An equivalent tooling can help exploring you repo and interact with it without relying on the UI.
IT can also help exploring the UI more efficiently if needed.
requirements:
xet open <file>, download the file (or straight in memory) and open it with a default local app.
xet open <directory>, open the uri in the UI on the default browser.
Use cases
View a single image, text file, pdf, notebook to verify or "peek" at configurations, or a line of code.
If you sync to S3 or GitHub, or you just uploaded a file and want to verify it - you can open the directory URI and see it with the latest commit.
Nice to have
xet open -i/--interactive which can open a text file and when closed, it commits the changes back - similar to an interactive git commit.
When running
open file
in bash, it opens in a default local app. An equivalent tooling can help exploring you repo and interact with it without relying on the UI. IT can also help exploring the UI more efficiently if needed.requirements:
xet open <file>
, download the file (or straight in memory) and open it with a default local app.xet open <directory>
, open the uri in the UI on the default browser.Use cases
Nice to have
xet open -i/--interactive
which can open a text file and when closed, it commits the changes back - similar to an interactive git commit.