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

Support for non-default standard input #1

Open
SquircleSpace opened this issue May 5, 2018 · 1 comment
Open

Support for non-default standard input #1

SquircleSpace opened this issue May 5, 2018 · 1 comment

Comments

@SquircleSpace
Copy link

I'm looking at using linedit for one of my projects (https://github.com/bradleyjensen/shcl). I have, shall we say, unusual requirements. I do weird things with *standard-input*, for example. Your README says that the consequences are unspecified if *standard-input* has been modified.

Can I get a slightly stronger guarantee than "literally anything can happen if you rebind *standard-input*"?

@SquircleSpace
Copy link
Author

Here are some more details.

My standard input is backed by a file descriptor, and I can produce that fd when needed. Notably, standard input might not be backed by fd 0. Throughout the lifetime of the program, standard input might end up being backed by different file descriptors, but it won’t change while reading input from the user. So, in any given invocation of linedit, the file descriptor is constant.

Would my use case be hard to support? Are there any sharp edges I need to look out for?

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