Allow to specify language #34
Labels
No labels
Compat/Breaking
Kind
Bad merge
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
New language
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: mergiraf/mergiraf#34
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It looks like mergiraf relies only on the file extension for language detection. I just ran into a conflict of a
.hhfile, but mergiraf says it doesn't know how to handle that despite it being some standard C++ header file. A CLI flag to manually specify the language for some cases would be helpful.That would make sense indeed, thanks for suggesting.
I've hacked this in
b3e99c0560. Not sure if this is the way as I'm not comfortable enough in Rust and it lacks tests.That sounds like a very sensible start! I don't know if the existing names in the language profiles are good enough as identifiers to be passed via the CLI. We could adapt them or introduce a separate field for it if needed.
I did this and only found this issue afterwards. One thing I did differently is that the command line language overrides automatic detection. The classic case I ran into this for is that
.plis the extension for both Prolog and Perl, so manual intervention is required in such cases.See #296.
Closed by #327