[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: [zzdev] Re: [zzdev] Yesterday's discussion, re inference
- To: "B. Fallenstein" <b.fallenstein@xxxxxx>
- Subject: Re: [zzdev] Re: [zzdev] Yesterday's discussion, re inference
- From: Tuomas Lukka <lukka@xxxxxxxxxx>
- Date: Wed, 23 May 2001 17:46:23 +0300
- Cc: zzdev@xxxxxxxxxx
- In-reply-to: <3B0BCA89.BCA3CBDE@xxxxxx>; from b.fallenstein@xxxxxx on Wed, May 23, 2001 at 04:34:49PM +0200
- Mail-followup-to: "B. Fallenstein" <b.fallenstein@xxxxxx>, zzdev@xxxxxxxxxx
- References: <20010523130004.K23534@xxxxxxxxxxxxxx> <3B0BCA89.BCA3CBDE@xxxxxx>
On Wed, May 23, 2001 at 04:34:49PM +0200, B. Fallenstein wrote:
> Tuomas Lukka wrote:
> > On IRC, benja and Stugge discussed inference. One point that comes
> > to me is that an inference system that changes the user's inputs
> > based on later inputs is usually not good; for example, debian's dselect
> > does this and it is not good.
> True! I'm not familiar with deselect, but I do know the problem from
> other fields. The rule of thumb I stated yesterday seems to apply here, too:
> 1) Show as much information as possible, even if it conflicts.
> 2) Don't change anything when there's a conflict.
Yes, I misread 2) from the scrollback, that's why I sent this.
> cell from an inferred list, for example a TODO list compiled from
> different other lists, might be meant to excise the cell also from the
> dimensions used for inferring,
A good example. And a very difficult one to handle...