Subject: bug#76769: 31.0.50; marking inconsistency between VC-Dir and dired-vc-next-action

From: Eli Zaretskii <[email-masked]>
Date: Mon, 10 Mar 2025 17:47:39 +0200

> From: Sean Whitton <[email-masked]>
> Cc: [email-masked],  [email-masked],  [email-masked],
>   [email-masked]
> Date: Mon, 10 Mar 2025 13:01:46 +0800
> 
> On Sat 08 Mar 2025 at 12:48pm +02, Eli Zaretskii wrote:
> 
> >> From: Sean Whitton <[email-masked]>
> >> Date: Sat, 08 Mar 2025 10:50:01 +0800
> >>
> >> Here's an alternative proposal that sits only at the UI level.
> >>
> >> A defcustom with values nil, 'ask, t.  nil is the current behaviour.
> >> 'ask means to do the follow things after a y/n prompt, t means to do
> >> them unconditionally:
> >>
> >> - When you try to mark a file but you can't because the directory is
> >>   already marked, unmark the directory first.
> >>
> >> - When you try to mark a directory but you can't because a file under it
> >>   is already marked, unmark all files under it and mark the directory,
> >>   instead.
> >
> > What about unmarking -- how will that work in your proposal?
> 
> Just the same as it does now, I think.

So one will be able to mark files easily and conveniently, using these
new features, but will be unable to unmark files with the same
convenience?