# from Ovid
# on Monday 18 August 2008 09:14:
>Moving forward is so much more satisfying than "did not/did too"
> discussions.
Now if only there were somewhere to move forward to. My thought was
that a more sophisticated presentation of complicated have/want could
be accomplished using a pair
--- On Mon, 18/8/08, Ovid <[EMAIL PROTECTED]> wrote:
> out who's to blame? Moving forward is so much more
> satisfying "did not/did too" discussions.
more satisfying THAN "did not/did too" discussions.
And learning how to write is more satisfying still.
Cheers,
Ov ...
--
Buy the book
--- On Mon, 18/8/08, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
> From: Eric Wilhelm <[EMAIL PROTECTED]>
> # from David Cantrell
> # on Monday 18 August 2008 04:07:
>
> >> > get remote GUIs to work
> >>
> >> That's not what I said ;-) See, the remote ...
> >
> >You were talking about ... So yes, it
# from David Cantrell
# on Monday 18 August 2008 04:07:
>> > get remote GUIs to work
>>
>> That's not what I said ;-) See, the remote X session is a protocol
>
>You were talking about doing GUI stuff. You mentioned running tests
> on another machines. So yes, it is what you said.
No, I didn't
On Thu, Aug 07, 2008 at 11:43:00AM -0700, Eric Wilhelm wrote:
> # from David Cantrell
> > Please don't take focus away from the window I'm working in. Please
> > don't cover up any of the many windows I've carefully arranged so that
> > I can see everything I need.
> I would say it only appears if
# from Aristotle Pagaltzis
# on Thursday 07 August 2008 23:41:
>It’s not 1998 anymore, you can easily have your terminals keep
>40,000 lines of scrollback or however many. And if you expect
>reams of output, you open a fresh terminal for it. Problems
>solved.
Oh, hey. Thanks for solving that. M
* Eric Wilhelm <[EMAIL PROTECTED]> [2008-08-07 23:35]:
> 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?
It’s not 1998 anymore, you can easily have your terminals keep
40,000 lines of scrollback or however many.
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 scroll
--- On Thu, 7/8/08, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
> 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?
I don't have to scroll back at all. I just have my tests die on first failure.
use Test::Most q
# from Andy Armstrong
# on Thursday 07 August 2008 12:49:
>> 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
On 7 Aug 2008, at 19:43, Eric Wilhelm wrote:
Please don't take focus away from the window I'm working in. Please
don't cover up any of the many windows I've carefully arranged so
that
I can see everything I need.
I would say it only appears if the tests failed. I would prefer
that to
ta
# from David Cantrell
# on Thursday 07 August 2008 05:57:
>Please don't take focus away from the window I'm working in. Please
>don't cover up any of the many windows I've carefully arranged so that
> I can see everything I need.
I would say it only appears if the tests failed. I would prefer t
On Wed, Aug 06, 2008 at 08:17:09PM -0700, Eric Wilhelm wrote:
> I bet that would be prettier in a GUI. We all develop on teletypes, eh?
> Perhaps something involving TAP and diagnostics could be used to cause a
> graphical program to run (egads! a graphical program!) on your shiny
> widescreen
# from Michael G Schwern
# on Wednesday 06 August 2008 19:49:
>Maybe line them up and space them out?
>
># ++--+--+
># | Elt|Got |Expected |
># ++--+--+
># | 0|id, name |id, name |
># * 1|1, Bob |2, Bob *
># ++--+--+
>
14 matches
Mail list logo
