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

lispyscript's ".ls" file extension overlaps with livescript #63

Closed
darrencruse opened this issue Nov 7, 2015 · 1 comment
Closed

lispyscript's ".ls" file extension overlaps with livescript #63

darrencruse opened this issue Nov 7, 2015 · 1 comment

Comments

@darrencruse
Copy link
Contributor

this is admittedly a low priority thing (I don't know there's anything to be done about it).

but I just wanted to create this issue as a note of this overlap in the use of ".ls" with "livescript" (another compile to javascript language) as can be seen here: http://livescript.net/#usage

I ran into the issue when working on an atom editor preview for lispyscript - the editor kept thinking my file was livescript not lispyscript.

To avoid the conflict in my experimental lispyscript branch (now renamed to "sugarlisp" after discussing with Santosh to avoid confusion with the new Lispyscript 2 effort), I'm supporting both the ".ls" extension for backward compatibility and an alternative (tbd) extension as well.

I just noticed the Lispyscript 2 project is already using ".ls2" so they've avoided the issue anyway:
https://github.com/geekskool/lispyscript2/tree/master/lispytest

Feel free to close this issue if desired - I'd just meant some time back to record the issue and never did.

I guess it's really only a problem in Lispyscript 1 if others want such an atom preview for Lispyscript 1 - in which case adding support for an alternative to the ".ls" file extension might be worthwhile.

@darrencruse
Copy link
Contributor Author

Closing - this was just something I'd wanted to share - nothing to be done.

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