unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 21315@debbugs.gnu.org
Subject: bug#21315: 25.0.50; doc of `kill-ring-save', `copy-region-as-kill' - bad
Date: Fri, 21 Aug 2015 10:17:56 -0700 (PDT)	[thread overview]
Message-ID: <fc2203ff-88da-4b92-a049-1606ef40d38c@default> (raw)

In Emacs 24.4 you changed not only the signature of these commands but
also their interactive behavior, by adding optional arg REGION and
giving users control over it with the prefix arg.

Unfortunately, the doc for this new behavior is horribly inadequate.

1. The Emacs manual says nothing about the new behavior.  It should
   cover it.

2. The doc strings are awful in this regard.  They say only "The
   optional argument REGION if non-nil, indicates that we're not just
   copying some text between BEG and END, but we're copying the region."

   That's worse than saying nothing - a complete cop-out.  If the doc is
   going to say something like "we're copying the region" and if that
   phrase is expected to mean anything then the doc needs to say what it
   means by that.  Describe the user-observable behavior difference
   between using a prefix arg and not using it.

   Currently, the use of a prefix arg is not even mentioned.  As bad as
   the description of parameter REGION is, it is not even connected with
   the use of a prefix arg.

3. The command is not documented at all in the Elisp manual.  It need
   not be, but the current state is that a user has no real information
   about this at all, and that is not good.

4. I find nothing in NEW for Emacs 24.4 (when this was released) about
   this.  User-observable behavior changes like this should be
   documented there.

<rant>Developers should not be allowed to commit program changes like
this without updating the doc appropriately.  Yes, leader resources are
scarce, and people are overworked.  But it's too bad, as it fosters bad
habits, unless the person who committed the code change happens to be
the one who fixes this doc bug, and can thus learn from the
mistake.</rant>

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-07-31 on LEG570
Bzr revision: 8d332aeccab2208e6c6bd434738565e6abf12043
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --host=i686-pc-mingw32 --enable-checking=yes,glyphs'





             reply	other threads:[~2015-08-21 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 17:17 Drew Adams [this message]
2015-12-04 18:06 ` bug#21315: 25.0.50; doc of `kill-ring-save', `copy-region-as-kill' - bad Drew Adams
2015-12-05 23:12   ` Juri Linkov
2015-12-06  2:13     ` Drew Adams
2015-12-06 16:15       ` Eli Zaretskii
2015-12-06 16:15     ` Eli Zaretskii
2015-12-08  0:49       ` Juri Linkov
     [not found] <<fc2203ff-88da-4b92-a049-1606ef40d38c@default>
     [not found] ` <<0fc80688-9028-4715-b2d9-a4bce4439a3b@default>
     [not found]   ` <<87y4d8cwwv.fsf@mail.linkov.net>
     [not found]     ` <<c9793b16-b42f-4094-8292-70682c50a22b@default>
     [not found]       ` <<83si3feepi.fsf@gnu.org>
2015-12-06 16:54         ` Drew Adams
2015-12-07 16:23           ` 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=fc2203ff-88da-4b92-a049-1606ef40d38c@default \
    --to=drew.adams@oracle.com \
    --cc=21315@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).