-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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: Add action to open text files in the default text editor #16636
Comments
It sounds like you're requesting to display 'open with' in the toolbar, can you confirm? |
Essentially, but it would open with the default text editor in one click rather then a prompt. |
Why not set it as the always open option. |
I can see this being a split button where the main button is 'open' and the drop down section displays the other options. |
Let's discuss this on Discord
|
After some discussion, we've determined that the underlying use case can be achieved by setting a custom argument for 'open with' (see #15141). However, adding a built-in action can simplify things, ensuring that the action always uses the default text editor, even if the user changes it in the future. In contrast, if the user sets a custom argument, they would have to update it manually. |
What feature or improvement do you think would benefit Files?
A button to the toolbar should be added to open text files (any file detected as containing standard format text) in the default editor - this could either be a setting or just automatically select the default editor for text on the user's computer (the latter is probably better)
This would allow for easy opening of unidentified files and serves as an indicator to the file's contents. It would make it easier to open text files as some programs may register them (e.g. if I want to edit a Visual Studio Solution file it wouldn't be as easy as double clicking as doing so would open it in Visual Studio instead of a text editor).
Requirements
Files Version
3.8.5.0
Windows Version
10.0.22631.4391
Comments
No response
The text was updated successfully, but these errors were encountered: