unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: Drew Adams <drew.adams@oracle.com>
Cc: 'Stefan Monnier' <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: `mouse-save-then-kill' changes
Date: Mon, 8 Nov 2010 10:11:02 +0100	[thread overview]
Message-ID: <20101108091101.GA5199@tomas> (raw)
In-Reply-To: <7A994E9631EC4CA18888238DFF8EB246@us.oracle.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Nov 07, 2010 at 08:42:01PM -0800, Drew Adams wrote:
> > I obviously can't, since I don't know what you're actually doing.

[...]

> I don't see how a hook would help, since I want to do something other than, not
> something in addition to, deleting/killing the region.

I can see how a hook would help here: to the programmers of the "layer
below" it signals. "careful, the user is supposed to change
functionality here". Whereas your approach of flet-binding a function,
while cute, would prevent changing any innards of Emacs for the fear of
breaking some hack as this. I can understand that that does not fly.

A hook -- why not? When the hook is there, don't run those three lines
of code. Or more flexible: use an "abnormal hook" and decide depending
on the return value of the hook function(s) (they tell the lower layer
"I've taken care of this" vs. "Do your own default thing").

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFM176lBcgs9XrR2kYRArrfAJoDPC9JzUp6WFE8VAAEm4Z2dFgNbgCcCmG2
3qgI7uTy+VyPSNC+7UNmT+U=
=N48m
-----END PGP SIGNATURE-----



      reply	other threads:[~2010-11-08  9:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 17:49 `mouse-save-then-kill' changes Drew Adams
2010-11-07 19:01 ` Stefan Monnier
2010-11-07 20:36   ` Drew Adams
2010-11-08  3:38     ` Stefan Monnier
2010-11-08  4:42       ` Drew Adams
2010-11-08  9:11         ` tomas [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=20101108091101.GA5199@tomas \
    --to=tomas@tuxteam.de \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).