You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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*"?
The text was updated successfully, but these errors were encountered:
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?
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*
"?The text was updated successfully, but these errors were encountered: