emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#57278: closed (26.3; Doc of `delete-indentation')


From: GNU bug Tracking System
Subject: bug#57278: closed (26.3; Doc of `delete-indentation')
Date: Thu, 18 Aug 2022 15:48:01 +0000

Your message dated Thu, 18 Aug 2022 08:47:08 -0700
with message-id 
<CADwFkmns-YeBtsGjoyhg9EcOV_PPeoWy6uDkgZgjnLujZVHcQg@mail.gmail.com>
and subject line Re: bug#57278: 26.3; Doc of `delete-indentation'
has caused the debbugs.gnu.org bug report #57278,
regarding 26.3; Doc of `delete-indentation'
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
57278: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57278
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 26.3; Doc of `delete-indentation' Date: Thu, 18 Aug 2022 14:29:08 +0000
The doc string and the description in (elisp) `User-Level Deletion' are
insufficiently oriented to end usage.  They should say clearly that a
prefix argument joins this line to the next one.

The doc string talks about "argument".  It should say "a prefix
argument".  The manual says nothing about the prefix argument.  It talks
only about argument JOIN-FOLLOWING-P.

Please write the descriptions first of all with interactive use in mind,
speaking of the prefix arg.  Then say that when called from Lisp the
argument corresponds to the prefix argument when used interactively.

In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
 of 2019-08-29
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor `Microsoft Corp.', version 10.0.19044
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install 'CFLAGS=-O2 -static -g3''




--- End Message ---
--- Begin Message --- Subject: Re: bug#57278: 26.3; Doc of `delete-indentation' Date: Thu, 18 Aug 2022 08:47:08 -0700
Drew Adams <drew.adams@oracle.com> writes:

>> These kinds of bug reports from you would be much more useful if they
>> were based off the latest code in master
>
> Please feel free to do that.  Or to close the bug if
> you feel it no longer exists.

I looked at it, and I think it's been fixed already.  Closing, thanks.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]