Re: [Patch] Behavior of dired when there already is a dired buffer of the same directory

["Richard M. Stallman" <rms@gnu.org>]

    > In general, prompting the user for optional information is a bad idea,
    > and this is especially true for "asynchronous" events.

    I agree, but it's also true that we do exactly that for plain files,
    which is a much more common case, so this same argument would call for
    a similar change to plain files.

Plain files are less likely to change while you have them visited.
If they do, continuing to edit the old contents is probably a grave mistake.

Precisely because this is a rather grave occurrence,
it would be a mistake to revert without telling the user.
Asking the user the question of whether to revert is an ideal
way to inform the user of the anomaly.

Directories often change while you have them in Dired, and that is not
an anomaly.  Continuing to operate on the Dired buffer is probably ok.
Reverting it automatically would be ok, but it is too slow.
I think the message now used is just the right behavior.