Skip to content
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 Request]: Let user define file extensions that should use the .txt thumbnail preview. #761

Open
3 tasks done
Olkris2666 opened this issue Feb 1, 2025 · 2 comments
Labels
Priority: Low Doesn't require immediate attention Type: Enhancement New feature or request Type: UI/UX User interface and/or user experience

Comments

@Olkris2666
Copy link

Checklist

  • I am using an up-to-date version.
  • I have read the documentation.
  • I have searched existing issues.

Description

Many "file formats" are just .txt with a different file extension.
e.g. : .md / .json / .bat

Solution

It would be cool if the user could right click a file with a certain uncommon file extension, and tell TagStudio "yes, this is actually just a .txt", that way TagStudio can treat it as such and display its contents.

Alternatives

No response

@Olkris2666 Olkris2666 added the Type: Enhancement New feature or request label Feb 1, 2025
@CyanVoxel CyanVoxel added Type: UI/UX User interface and/or user experience Priority: Low Doesn't require immediate attention labels Feb 1, 2025
@CyanVoxel CyanVoxel moved this to 🍀 Backlog in TagStudio Development Feb 1, 2025
@SkeleyM
Copy link
Contributor

SkeleyM commented Feb 1, 2025

would this be as a file to file basis like this:
Image

or as a 'treat every file with this extension as txt' kind of thing

@CyanVoxel
Copy link
Member

Text is also very specific, naturally if the user is given an option to try and render a file extension with an internal renderer outside it's known MIME type then they should at least have the option to choose from any of the types of renderers we have, not just text.

I also don't think this should be an right-click option on each file but rather a global setting that overrides known file extension MIME types with a user-specified renderer.

As a much simpler alternative, I noticed this feature request came from wanting to associate a specific file type as a text file. We could just add that to the list of text files in our internal lists since it doesn't seem to be hitting any matches with the MIME type fallback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low Doesn't require immediate attention Type: Enhancement New feature or request Type: UI/UX User interface and/or user experience
Projects
Status: 🍀 Backlog
Development

No branches or pull requests

3 participants