unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 18088@debbugs.gnu.org
Subject: bug#18088: 24.4.50; `region-extract-function': (1) NEWS, (2) return value
Date: Sat, 30 Apr 2016 00:31:11 +0200	[thread overview]
Message-ID: <878tzwm4i8.fsf@gnus.org> (raw)
In-Reply-To: <c7faf15a-9001-41aa-9a3e-08ea87e119c9@default> (Drew Adams's message of "Wed, 23 Jul 2014 09:04:55 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> Variable `region-extract-function' was apparently added in Emacs 24.4.
> It is used in several key places that affect killing or deleting text.
>
> 1. It should be called out in NEWS, saying what user-visible behavior
>    its presence changes.
>
> 2. The doc string points out that, depending on the value of its
>    argument, its return value is (a) significant and specified or (b)
>    insignificant and undefined.
>
>    This is the first time I have seen this for an Emacs function
>    distributed with GNU Emacs.  Certainly it is the first time I've
>    seen such odd behavior documented.
>
>    This does NOT seem like the kind of thing we should be doing - let
>    alone *encouraging* by defining a variable whose value will be
>    user-defined functions that have such twisted behavior.
>
>    Is this unusual design necessary?  Seems to be sloppy, error prone,
>    and an invitation to bad programming habits by users.

It seems like a quite complicated thing, but as it has been in a release
now, I think it's too late to do anything about that.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2016-04-29 22:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 16:04 bug#18088: 24.4.50; `region-extract-function': (1) NEWS, (2) return value Drew Adams
2016-04-29 22:31 ` Lars Ingebrigtsen [this message]

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=878tzwm4i8.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18088@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 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).