unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: 38392@debbugs.gnu.org
Subject: bug#38392: zap-up-to-char should appear in "Deletion and Killing" Emacs info section and "Command Index"
Date: Thu, 28 Nov 2019 13:45:20 +1300	[thread overview]
Message-ID: <e5e9a1741465d96f90c88f07aaf2ce65@webmail.orcon.net.nz> (raw)
In-Reply-To: <CAEndGgT_sVPheaFLHxYNiUX2wmz+JsQkyXNnVa=5Y51ZjJhFJA@mail.gmail.com>

Eli wrote:
> I'm not sure we should have it in the manual.  The fact that you
> wanted it doesn't yet mean it's useful enough to have in the manual.
> 
> Does anyone else have an opinion?

Mentioning only one of the two commands just seems arbitrary,
so I think it should be either "both" or "neither" for the sake
of consistency.

I think the manual should mention both of them, and that their
docstrings should probably mention one another as well, so that
users can learn about these alternatives more easily.


-Phil






  reply	other threads:[~2019-11-28  0:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 18:34 bug#38392: zap-up-to-char should appear in "Deletion and Killing" Emacs info section and "Command Index" Justin Paston-Cooper
2019-11-26 19:45 ` Eli Zaretskii
2019-11-26 19:47   ` Justin Paston-Cooper
2019-11-26 20:05     ` Eli Zaretskii
2019-11-27 10:11       ` Justin Paston-Cooper
2019-11-27 15:40         ` Drew Adams
2019-11-27 15:57           ` Justin Paston-Cooper
2019-11-27 16:04             ` Drew Adams
2019-11-27 16:05               ` Justin Paston-Cooper
2019-11-27 16:44                 ` Drew Adams
2019-11-27 19:35                   ` Justin Paston-Cooper
2019-11-27 21:46                     ` Drew Adams
2019-11-27 22:10                       ` Justin Paston-Cooper
2019-11-28  0:45                         ` Phil Sainty [this message]
2019-11-28 12:48                           ` Lars Ingebrigtsen
2019-11-29 12:15                             ` Stefan Kangas
2019-12-05  9:56                               ` Lars Ingebrigtsen
2019-11-29 10:19                           ` Eli Zaretskii
2019-11-28  9:20           ` Stefan Kangas
2019-11-28 16:42             ` Drew Adams
2019-11-27 15:54         ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=e5e9a1741465d96f90c88f07aaf2ce65@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=38392@debbugs.gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).