You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The usage info for the tool does not show all supported input file types. So unless the user looks at the sourcecode they might not realise there are other types that are supported. I came across this issue trying to access a save file, but there was no "save" filetype listed in usage so couldnt work out what i was doing wrong until i looked at the sourcecode.
Since there are quite a few options for the intype parameter it might help to list them in usage in alphabetical order? Also group together the different intypes that are equivalent since users may not be aware they are the same thing.
The resulting usage is a lot longer, but since filetype is required to correctly perform any action it seems worthwhile.
PR #88 only adds the "save" type.
Still missing after that are:
nca0romfs/nca0_romfs/betaromfs/beta_romfs
nso0
Also still missing is the inclusion of the equivalent types, such as: pfs0/exefs instead of just pfs0.
This would help n00bs like me who might not be aware that pfs0 and exefs are the same thing. This goes for all equivalencies, not just the pfs0 one I used as an example.
The usage info for the tool does not show all supported input file types. So unless the user looks at the sourcecode they might not realise there are other types that are supported. I came across this issue trying to access a save file, but there was no "save" filetype listed in usage so couldnt work out what i was doing wrong until i looked at the sourcecode.
So need to make this usage:
match these available options
Since there are quite a few options for the intype parameter it might help to list them in usage in alphabetical order? Also group together the different intypes that are equivalent since users may not be aware they are the same thing.
The resulting usage is a lot longer, but since filetype is required to correctly perform any action it seems worthwhile.
So perhaps something like:
The text was updated successfully, but these errors were encountered: