-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Build out shell a bit more #5082
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
Conversation
|
Responding to your email…
And the concern I'd have with just using |
|
I'll put in the code that emulates the interactive shell then! |
|
@benfry With the latest commit: Gives me the same the same PATH from inside Processing compared to when query this in the terminal. (Tested on macOS.) |
|
Also tested on latest Raspbian. |
|
Also the null/non-null thing is going to be a problem in code: I think you're gonna need to cast the null to a Do we really need an additional version with just stdout? I lean toward just keeping it simple… either you want the output or not, and my general experience has been that programs are inconsistent enough about what goes in err and what goes in out… |
|
Double-checked the situation with the variable number of arguments - seems to work 👍 Thinking a bit about my use cases: stderr is certainly useful for user-facing errors, but in many situations I'd forgo the extra line that constructs its You bring up a good point that stdout vs stderr isn't really so consistent anyway. Is there a possibility of combining both streams in a way that keeps the temporal ordering, perhaps? (On UNIX one could alternatively do |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |


No description provided.