Request for a "Save" Mode for terminalfilechooser and Implementation Proposal #2673
smartapplez
started this conversation in
3. Ideas
Replies: 1 comment
-
If you don't want to accidentally overwrite other files, or just want to make sure only the Instead of writing directly to the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I acknowledge that it's in Yazi's nature to "select/open" files, which makes it an amazing option for a terminal-file-chooser, and it is proving its effectiveness through the link provided in the yazi/docs/tips website hunkyburrito.xdg-desktop-portal-termfilechooser. However, whenever one goes into "saving" mode (or trying to save a file in other words), the yazi file manager defaults to overwriting the file that is being selected when "Open" keybind is pressed, which currently makes it inconvenient when trying to save a new file.
One idea I propose to further extend its usefulness for a terminalfilechooser standpoint is to have a "save" mode to where the user can toggle off the "selection" cursor to imply to save a new file in the current directory that yazi is in. And the user can toggle on the "selection" cursor to imply that it will overwrite a file. Let me know if there are any other ideas for how the "save" mode should be implemented in yazi. This will make it easier for plugins/packages to interface with yazi and let them know what action to take.
Beta Was this translation helpful? Give feedback.
All reactions