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
Judging from the included example, BridleNSIS scripts don't have their own file-extension, but use the same as vanilla NSIS (.nsi and .nsh). However, the transpiled scripts use different file extensions (.bnsi and .bnsh.) In my opinion that's rather confusing and really should be the other way around.
To add to the confusion, the USAGE file claims the transpiled (or “converted”) scripts will be named differently (.snsi and .snsh) – which is not the case.
Ideally, the BridleNSIS scripts file would have a file-extension other than vanilla NSIS, so code editors can tell them apart without the user having to specify the syntax specifically. I see no reason why the output, which is vanilla NSIS, would use different file extensions. If you want to ”mark” the transpiled files, you could prepend a comment such as // Generated by BridleNSIS.
Lastly, it doesn't seem like you plan to continue to work on BridleNSIS, yet I wanted to post an issue for the case somebody else want's to take over and address open issue.
The text was updated successfully, but these errors were encountered:
Judging from the included example, BridleNSIS scripts don't have their own file-extension, but use the same as vanilla NSIS (
.nsi
and.nsh
). However, the transpiled scripts use different file extensions (.bnsi
and.bnsh
.) In my opinion that's rather confusing and really should be the other way around.To add to the confusion, the
USAGE
file claims the transpiled (or “converted”) scripts will be named differently (.snsi
and.snsh
) – which is not the case.Ideally, the BridleNSIS scripts file would have a file-extension other than vanilla NSIS, so code editors can tell them apart without the user having to specify the syntax specifically. I see no reason why the output, which is vanilla NSIS, would use different file extensions. If you want to ”mark” the transpiled files, you could prepend a comment such as
// Generated by BridleNSIS
.Lastly, it doesn't seem like you plan to continue to work on BridleNSIS, yet I wanted to post an issue for the case somebody else want's to take over and address open issue.
The text was updated successfully, but these errors were encountered: