On 7 Aug 2008, at 22:34, Eric Wilhelm wrote:
I would say it only appears if the tests failed. I would prefer
that to
take focus rather than needing to go activate it. Would you rather
scrollback to read the diagnostics in your terminal?
Is that so odd? Emphatically YES - I would rather scrollback in the
terminal than have random stuff opening elsewhere. Always! :)
So how far do you scroll back, how do find the error message, and what
happens when the root cause has outrun the history buffer? And did
you
notice that everything is backwards when you start at the end?
It's probably not terribly germane to this discussion - but since you
asked...
I'm using Mac OS Terminal which maps Cmd-K to clear buffer. It clears
both the screen and the scrollback. And I have pretty much infinite
scrollback configured. When I'm running tests I usually Cmd-K before
running the tests. If there's a failure I can find it with Cmd-F or -
more often - just scroll back to it - which is simplified by not being
able to scroll off the top.
The computer has the information required to display the first error
first, but I guess solving technology problems with people is the
better worse.
I'm in favour for better user interfaces; I don't think it's currently
perfect. I just don't like either jumping out of my terminal session
unexpectedly or having to go looking for a new window that's popped up
somewhere.
--
Andy Armstrong, Hexten
