Let user configure all filetypes, use system's default as fallback
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 275
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
It may make sense to add a filetypes subsystem, apart from the OS' delivered one, where the user can define actions. Care would be needed to be taken, when a filetype can be two or more types. This often happens when the container is a Zip archive (OpenDocument Format, ePub, eComics, etc.). Then the filetype would be a sublcalss of the container format.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the existing file-opening behavior and how the system default is selected; the issue names no files, tests, or entry points. Define the scope for user-configurable filetype actions, including formats with multiple container or content types, and establish how fallback behavior will be verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100