-
Notifications
You must be signed in to change notification settings - Fork 62
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
Support for code piped through stdin #78
Comments
Just thought about... But how we should handle Ctrl+r code reloading? |
Not possible I guess. Other way of achieving the same is have an option to pass a command to get the code. Having the command, then you could just run the command again.
|
But I like this pipe idea 😄 Maybe we can access piped terminal commandline text to repeat the preprocess. |
The place where terminal history is saved varies depending on the shell :/ |
Yes I know and it seems there is no module out there solving this... |
I succesfuly got access to Line 17 in e844eac
But having trouble to access Line 11 in e844eac
I Created a test script at Line 16 in e844eac
pipe-test
May be someone can help out? |
Sorry @aristidesfl this cannot work native on Microsoft Windows. We can only ugly work around when we use a temporary file to share piped result with |
It wouldn't matter how it is implemented as long as the complexity would be hidden from the user :) That way the simple "bash script" only had to be written once in node-iron in the form of pipe support. |
I want give it a try, but should we store the tempfile in the working directory? it has an impact on later required files. |
@aristidesfl could you please test if this works for you by installing from repo?
|
This would allow any transpiler to be used on the fly without extra files or configuration.
Examples:
babel app.es6 | node-iron
coffee -p app.coffee | node-iron
The text was updated successfully, but these errors were encountered: