Re: Another proposal for frontends and queries.

[Joel Brobecker <brobecker@adacore.com>]

> Having just "<enter>" behave differently depending on a setting, is
> bad UI/usability, IMO.  If you switch to 'query', you force the user to
> type 'y' or 'n' explicitly, which is a Good Thing.

I agree.

Hui:

You keep suggesting more of the same - basically, your suggestions
so far revolve around the same principle, which is adding an extra
setting that controls the query being made. But we have already
explained that this is something we would like to avoid, and we
explained why. In the meantime, the issue remains unresolved and
people like Marc continue being stuck with it.

There are two aspects to this issue:

  1. A specific short-term need: The default for queries in precord
     is 'n', and that causes auto-answers in Eclipse to be 'n' as
     well.  As a result, Eclipse uses cannot use precord fully.

     The answer to that problem is very simple: Do *NOT* provide
     a default answer. That's what "query" does.

  2. A longer-term issue: It should be possible for Front-Ends
     using GDB/MI to relay queries to the user, so that the user
     can enter confirmation before the operation is in fact
     executed.  That's longer term, as this needs some infrastructure
     work.

Right now, I'm only interested in (1). It's clear that you do not like
the idea of querying the user without providing a default. Can you
explain why?

-- 
Joel