ocide: FR to allow to set the editor of unknown file extensions
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 16
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Some projects use file extensions that are unknown to OCIDE but should be usable with C/C++ editor component.
Currently they are opened as text files, it would be nice to be able to create own mappings for the editor (specifying custom build steps is a separate issue [I think custom build steps aren't possible yet, but I haven't checked the documentation]).
A partially related issue is that it is likely reasonable to set the extensions "y" and "l" (yacc/bison and lex/flex) to the C/C++ editor component (if there's only a single for both, like it is the case with Visual Studio) as both file types in a project that is loaded via OCIDE will result in a C or C++ file (and therefore contains C / C++ parts).
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 tracing how OCIDE chooses an editor for unknown file extensions and how the C/C++ editor component is selected. Define completion as allowing project-specific editor mappings, while considering the mentioned yacc/bison (.y) and lex/flex (.l) extensions; custom build steps are explicitly separate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp
- Domain
- desktop, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100