all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 59934@debbugs.gnu.org
Subject: bug#59934: 28.2; Doc strings of `(kill|delete)-matching-lines'
Date: Sat, 10 Dec 2022 00:01:04 +0100	[thread overview]
Message-ID: <CAAeL0STJKtFJ51MAMmuruJMYAgt671byVCde7jgcF1DA4XO28g@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB548812D7B73919BB2A1ABC88F31C9@SJ0PR10MB5488.namprd10.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]

The docstring of `kill-matching-lines' already says (just at the end):

  If you merely want to delete the lines, without adding them to
  the kill ring, the M-x flush-lines command is faster.

but the one for `delete-matching-lines'/`flush-lines' does not mention the
kill- version.

On Fri, Dec 9, 2022 at 11:52 PM Drew Adams <drew.adams@oracle.com> wrote:

> These two doc strings are _very_ similar.  The two commands are
> presumably nearly the same, the difference being that one kills
> to the `kill-ring' and the other just deletes.
>
> Please consider, in each of these doc strings, adding a reference to the
> other command.  E.g., "See also `<other>-matching-lines', which is
> similar but <summarize the difference>."  That will make uses aware of
> the existence of the other command.  Sometimes users don't consider, or
> aren't even aware, of the difference between the two kinds of deletion.
>
> You might also explicitly point out the use case for `kill-*', e.g.,
> when giving the summary in the "See also": killing lets you subsequently
> yank the matching lines somewhere.  Doesn't hurt to point this out
> briefly.
>
> In GNU Emacs 28.2 (build 2, x86_64-w64-mingw32)
>  of 2022-09-13 built on AVALON
> Windowing system distributor 'Microsoft Corp.', version 10.0.19044
> System Description: Microsoft Windows 10 Pro (v10.0.2009.19044.2251)
>
> Configured using:
>  'configure --with-modules --without-dbus --with-native-compilation
>  --without-compress-install CFLAGS=-O2'
>
> Configured features:
> ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
> NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
> XPM ZLIB
>
> (NATIVE_COMP present but libgccjit not available)
>
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 2314 bytes --]

  reply	other threads:[~2022-12-09 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 22:51 bug#59934: 28.2; Doc strings of `(kill|delete)-matching-lines' Drew Adams
2022-12-09 23:01 ` Juanma Barranquero [this message]
2022-12-09 23:14   ` Drew Adams
2022-12-13  0:48     ` Stefan Kangas
2022-12-13  1:20     ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAeL0STJKtFJ51MAMmuruJMYAgt671byVCde7jgcF1DA4XO28g@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=59934@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.