Re: properties changed

Tõivo Leedjärv <[email protected]> Wed, 2 Apr 2025 20:08:43 +0200
Newsgroups gmane.network.unison.general
Message-ID <CAALvpZQY-0XggWJrWfbrq6O0z-e8s2xrQeJTjjUbrDugyDoz1g@mail.gmail.com>
On Wed, 2 Apr 2025 at 19:44, "Head Geek (伟思礼)" <[email protected]> wrote:

> On Apr 2, 2025, at 09:49, Tõivo Leedjärv <[email protected]> wrote:
> > For example, at the first file, press P (or =) to match all props
> changes, then key for your preferred propagation (], as you wrote) (or m
> for merge, if you've set that up), then D (or _) to unselect all props
> changes.
> > Alternatively, instead of unselecting props changes, you can invert the
> matching condition (press key X or !), selecting all non-props changes.
> Then you can for example skip (/ or : or -) all other changes to propagate
> only the props changes first and then do a separate sync for other changes.
>
> I don't get it.  On the first file, whether I press m or M or p or P, it
> just asks me again for the first file, without showing a change.  Over and
> over.


I don't know if this is a bug or if it's intentional but the matching
conditions apply to all following files, but not to the current one
prompted. So, you go P -> ] -> D -> ], basically match the selection, apply
the (]), unmatch the selection and then apply the (]) to the currently
prompted file. You have to list files (L or l) to see what has happened.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].