From: Drew Adams <drew.adams@oracle.com>
To: 18086@debbugs.gnu.org
Subject: bug#18086: 24.4.50; NEWS entry for `kill-region'
Date: Wed, 23 Jul 2014 09:16:56 -0700 (PDT) [thread overview]
Message-ID: <3236f48c-0797-49ca-ab5e-17a90c7e4e1d@default> (raw)
In-Reply-To: <2099c598-0d39-441d-92f8-f3bbc570a08b@default>
> From the beginning, and forever prior to Emacs 24.4, `kill-region' had
> this signature: (kill-region BEG END). That includes Emacs 24.3.
>
> Starting with Emacs 24.4, this is the signature:
> (kill-region BEG END &optional REGION)
>
> 1. This change should be called out in NEWS.
>
> 2. Instead, there is this entry in NEWS for Emacs 24.4, under
> "Incompatible Lisp changes in Emacs 24.4":
>
> ** `kill-region' has lost its `yank-handler' optional argument.
>
> This is incomprehensible. It never had a `yank-handler' optional
> argument.
I was apparently wrong about that last statement (and so too about
the first statement, that in 24.3 the function accepted only two args).
[However, I do not really understand, and have no time to research
this now: in Emacs 24.3, emacs -Q, `C-h f kill-region' does NOT
show parameter YANK-HANDLER. But in the 24.3 source file simple.el,
YANK-HANDLER is present. Perhaps the simple.elc distributed by GNU
is older than the addition of YANK-HANDLER to simple.el?]
The NEWS entry should state not that the YANK-HANDLER parameter
was removed but that it was replaced by the REGION parameter etc.
And of course there SHOULD have been a NEWS entry for 24.3,
stating that parameter YANK-HANDLER was added. If it is not too
late, that should be added now. Without it, mention of YANK-HANDLER
in the 24.4 entry makes no sense.
next prev parent reply other threads:[~2014-07-23 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 15:44 bug#18086: 24.4.50; NEWS entry for `kill-region' Drew Adams
2014-07-23 16:10 ` Andreas Schwab
2014-07-23 16:56 ` Drew Adams
2014-07-23 16:16 ` Drew Adams [this message]
2014-07-23 22:21 ` Stephen Berman
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=3236f48c-0797-49ca-ab5e-17a90c7e4e1d@default \
--to=drew.adams@oracle.com \
--cc=18086@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 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.