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

[Lennart Borgman (gmail)]

Stefan Monnier wrote:
>> It's also much more annoying for one's command flow to be interrupted by
>> an unexpected question prompt, and that can cause real problems in cases
>> where the user types commands quickly.
> 
>> 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.


Is not that a very different situation?

In the case of dired it is about what is displayed in Emacs. In the case
of files it is also about the content of a buffer and reverting can make
edits go away.