-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
ctrl+d ought result in EOF in ncdirect_readline() #2521
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
input
readin' dem bytes
Milestone
Comments
dankamongmen
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
input
readin' dem bytes
labels
Jan 3, 2022
we have: if(id == NCKEY_EOF || id == NCKEY_ENTER){
if(id == NCKEY_ENTER){
if(fputc('\n', n->ttyfp) < 0){
free(str);
return NULL;
}
}else if(wused == 1){ // NCKEY_EOF shouldn't this be catching it? |
perhaps relatedly, |
and ctrl+cing out of |
|
this followed a 2048 byte read |
so we need to be setting the input fd persistently high on the EOF case, for one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
input
readin' dem bytes
Currently, ctrl+d in
ncdirect_readline()
just results in a capital D that can be erased and composed. It ought instead trigger an EOF. I'm undecided as to whether any existing text ought be delivered first.See dankamongmen/growlight#154.
The text was updated successfully, but these errors were encountered: