https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
--- Comment #8 from Yakov ---
(In reply to Andreas Schwab from comment #7)
> This has nothing to do with gcc, it is a property of the terminal emulation.
ok. all my terminals have this problem)=
thanks for help
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
Andreas Schwab changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
--- Comment #6 from Yakov ---
(In reply to Jonathan Wakely from comment #5)
> (In reply to Yakov from comment #4)
> > I am sorry. I think, I did mistake in my question. I did not press Enter.
>
> You said "when the second line begins. symbols, e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
--- Comment #5 from Jonathan Wakely ---
(In reply to Yakov from comment #4)
> I am sorry. I think, I did mistake in my question. I did not press Enter.
You said "when the second line begins. symbols, entered in first line"
If that doesn't mean
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
--- Comment #4 from Yakov ---
(In reply to Jonathan Wakely from comment #2)
> If you're saying that data read from the terminal by std::cin cannot be
> "un-read" by typing backspace, that's correct. That is not a GCC bug, it's
> just how the OS w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
Yakov changed:
What|Removed |Added
Status|RESOLVED|WAITING
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
Yakov changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
--- Comment #2 from Jonathan Wakely ---
If you're saying that data read from the terminal by std::cin cannot be
"un-read" by typing backspace, that's correct. That is not a GCC bug, it's just
how the OS works.
In the default line-buffered mode,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86921
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
