I have the latest version of Console set up on my Windows XP 32bit box so I can run Cmd, Cygwin and Git Bash all within it - excellent stuff.
The only real problem I have with it, is that if in a cygwin (or git bash) shell, I start a process that takes a long time and produces a lot of output (such as an svn update or a compile or something), if I drag the scrollbar up (to look at the start of the output, while more is still being produced), the shell 'loses its place' and suddenly new output starts being produced at the higher scrollbar position.
This not only means that output is overwritten, but means it becomes harder to tell when its finally finished.
That's one of very few wrinkles in an otherwise excellent program. Anyone else get the same problem? Any workarounds/fixes possible?
Thanks,
Robin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've also seen this, but I haven't pinned down the exact circumstances that causes this. Usually it seems to happen to me when I'll scroll up to look at the output of something, put the cursor on the screen to highlight something, then hit enter. The expected behavior is to have the buffer pop back down to the bottom of the terminal instead of putting a prompt right there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For me Cygwin and bash behave this way - don't scroll to the bottom of the buffer - even in plain cmd.exe window. So, I don't think Console has anything to do with it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the latest version of Console set up on my Windows XP 32bit box so I can run Cmd, Cygwin and Git Bash all within it - excellent stuff.
The only real problem I have with it, is that if in a cygwin (or git bash) shell, I start a process that takes a long time and produces a lot of output (such as an svn update or a compile or something), if I drag the scrollbar up (to look at the start of the output, while more is still being produced), the shell 'loses its place' and suddenly new output starts being produced at the higher scrollbar position.
This not only means that output is overwritten, but means it becomes harder to tell when its finally finished.
That's one of very few wrinkles in an otherwise excellent program. Anyone else get the same problem? Any workarounds/fixes possible?
Thanks,
Robin
I've also seen this, but I haven't pinned down the exact circumstances that causes this. Usually it seems to happen to me when I'll scroll up to look at the output of something, put the cursor on the screen to highlight something, then hit enter. The expected behavior is to have the buffer pop back down to the bottom of the terminal instead of putting a prompt right there.
For me Cygwin and bash behave this way - don't scroll to the bottom of the buffer - even in plain cmd.exe window. So, I don't think Console has anything to do with it.