On Sun, Sep 11, 2022 at 12:18:04PM +0200, Omar Polo wrote:
> > blob - 65405972315ce384c286567d1765d330d8d9a13f
> > blob + 7f5838ca56a87f272be0f2ddb8af1b6feb75c238
> > --- tog/tog.1
> > +++ tog/tog.1
> > @@ -226,6 +226,12 @@ This can then be used to open a new
> >  view for arbitrary branches and tags.
> >  .It Cm @
> >  Toggle between showing the author and the committer name.
> > +.It Cm &
> > +Prompt for a pattern to display a log view limited to the subset of
> > +commits matching the provided pattern, which is an extended regular
> > +expression matched against a commit's author name, committer name,
> > +log message, and commit ID SHA1 hash.
> > +Use empty string as a pattern to display all commits.
> 
> nitpick: what if we move this after the /-key description and just say
> that has the same behavior but hides the non-matching commits?  We
> could drop some copy-paste then.

[...]

> blob - 65405972315ce384c286567d1765d330d8d9a13f
> file + tog/tog.1
> --- tog/tog.1
> +++ tog/tog.1
> @@ -189,6 +189,10 @@ against a commit's author name, committer name, log me
>  commit ID SHA1 hash.
>  Regular expression syntax is documented in
>  .Xr re_format 7 .
> +.It Cm &
> +Like
> +.Cm /
> +but hides the non-matching commits.
>  .It Cm n
>  Find the Nth next commit which matches the current search pattern (default: 1).
>  .br

Thank you for the input. One comment regarding the man page - shouldn't
we keep the sentence about empty pattern? - "Use empty string as a
pattern to display all commits."