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
While the tail -f command is command is running in the git bash terminal and hit the enter button 6 to 7 times
and entered some other command with out pressing the Ctrl-C.
At this point on pressing Ctrl-C, then behavior is not similar to putty.
In putty the new lines are not buffered.
Below is the screenshot from the Git-Bash windows terminal,
How can I control this behavior? any configuration changes?
My use case is while tailing the log files, we may hit the enter button multiple times for segregation purpose. But these lines are buffered in the terminal and the moment we hit the Ctrl-C, the control will scroll for that many times as shown above. This kind of behavior not observed in Putty.
More Details
Windows 10
Git Bash
latest
xterm
The text was updated successfully, but these errors were encountered:
While the tail -f command is command is running in the git bash terminal and hit the enter button 6 to 7 times
and entered some other command with out pressing the Ctrl-C.
At this point on pressing Ctrl-C, then behavior is not similar to putty.
In putty the new lines are not buffered.
Below is the screenshot from the Git-Bash windows terminal,
How can I control this behavior? any configuration changes?
My use case is while tailing the log files, we may hit the enter button multiple times for segregation purpose. But these lines are buffered in the terminal and the moment we hit the Ctrl-C, the control will scroll for that many times as shown above. This kind of behavior not observed in Putty.
More Details
The text was updated successfully, but these errors were encountered: