[debbugs-tracker] bug#30343: closed (make transpose-regions interactive)

[GNU bug Tracking System]

Your message dated Sun, 11 Mar 2018 12:11:19 +0100
with message-id <address@hidden>
and subject line Re: bug#30343: make transpose-regions interactive
has caused the debbugs.gnu.org bug report #30343,
regarding make transpose-regions interactive
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30343: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30343
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> make transpose-regions interactive
>
>
>
>
> Date: 
>
> Sun, 04 Feb 2018 10:37:22 +0100
>
>
>
>
> Package: emacs
> Version: 27.0.50
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#30343: make transpose-regions interactive
>
>
>
>
> Date: 
>
> Sun, 11 Mar 2018 12:11:19 +0100
>
>
>
>
> > Date: Sat, 10 Mar 2018 14:02:01 +0200
> > From: Eli Zaretskii <address@hidden>
> > CC: address@hidden
> > Reply-to: Eli Zaretskii <address@hidden>
> > 
> > This LGTM, thanks.  One minor comment:
> > 
> > > +Interactively, STARTR1 and ENDR1 are point and mark; STARTR2 and ENDR2
> > > +are the last two marks pushed to the mark ring; LEAVE-MARKERS is nil.
> > > +If a prefix argument N is given, STARTR2 and ENDR2 are the two
> > > +successive marks N entries backwards in the mark ring.  A negative
> > > +prefix argument instead counts forwards from the oldest mark in the
> > 
> > Please use "back" in "forward" here, instead of "backwards" and
> > "forwards".  ("Backwards" has a meaning that might confuse readers
> > here.)
>
> Thanks again for the review, it's pushed now with your doc fix.
>
> commit b88e7c8bcd523f1f503f87a1734679405322b5ec
> Date:   Sun Mar 11 11:59:01 2018 +0100
>
>   Make transpose-regions interactive (Bug#30343)
>   
>   * doc/emacs/fixit.texi (Transpose): Mention and explain the new
>   command.
>   * editfns.c (Ftranspose_regions): Add an interactive calling
>   specification, and add documentation for it.
>
>
> --- End Message ---