Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File extension confusion #4

Open
idleberg opened this issue Jul 2, 2017 · 0 comments
Open

File extension confusion #4

idleberg opened this issue Jul 2, 2017 · 0 comments

Comments

@idleberg
Copy link

idleberg commented Jul 2, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant