RE: C-x C-f, Tab (in)completion and visiting the wrong, new files

["Drew Adams" <drew.adams@oracle.com>]

> >>> But if the same happens to others as well, perhaps a more general
> >>> change could make Emacs more convenient in this respect.
> >> find-file-confirm-nonexistent-file
> > Could be done, but I don't think adding another confirmation
> step for new
> > files (that are intended to be created) is as good as making the right
> > guess when the user uses completion and confirms an incomplete
> > (i.e. ambiguous) choice.
>
> That's very interesting: I added the find-file-confirm-nonexistent-file
> pretty for the exact reason you describe, and what you propose is
> a refinement of it: to only do the "confirm" step if the previous command
> was a completion command.  That makes a lot of sense: it may even
> be enabled
> by default without provoking angry reactions, contrary to
> find-file-confirm-nonexistent-file.  It could just be confirgured
> with a new
> value `only-after-completion' for find-file-confirm-nonexistent-file.
>
> > This case may even be universal to all completion-based
> minibuffer inputs.
>
> Could be.

This proposal is essentially to require confirmation for lax completion.
With the `only-after-completion' value, confirmation would be required only
after TAB; any other non-nil value would always require confirmation for
input that doesn't match completely. Is that correct?

I have no objection to such an option to control the behavior, but I don't
think the default behavior should be changed.