all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: other-buffer advice on kill-buffer
Date: Thu, 4 Aug 2011 16:42:30 +1000	[thread overview]
Message-ID: <CAC=50j-F5fcCs-OW5x2LbdaX_xCTCP9Z0SP-=pmmE5OWs=NSWA@mail.gmail.com> (raw)
In-Reply-To: <87livb5885.fsf@fencepost.gnu.org>

On Wed, Aug 3, 2011 at 4:18 PM, David Kastrup <dak@gnu.org> wrote:
> Richard Stallman <rms@gnu.org> writes:
>
>>     That's not correct.  You can advise a primitive function, but the
>>     advice will only affect calls to that function made from Lisp, not
>>     calls from other primitives.
>>
>> It may be that in a few special cases
>> we should modify calls within C code to some primitive functions
>> so that they call the Lisp symbol.
>> That way, it would work to advise those functions.
>>
>> To do this for all the primitive functions would be impossible, I
>> think, and certainly not worth the pain.  But there might be a few
>> functions for which this would be particularly useful, and it might be
>> worth doing this for them.
>
> If it is worth making it advisable, it is worth giving it a hook.
>
> The problem is that advice is intended for adding functionality that has
> not been imagined previously.  So it is hard to think of a case where
> one would explicitly make a function advisable.
>
[
There is one special case where being able to add advice to more
functions, especially some primitive ones, accessibility. At least two
packages written to make emacs accessible to blind and vision impaired
users achieves this through advising functions. Currently, there are a
couple of places where accessibility is limited because of the problem
of advising primitive functions. So, adding this ability would likely
benefit at least one group of users and do so without any issue for
other users.

Tim



  parent reply	other threads:[~2011-08-04  6:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 23:03 other-buffer advice on kill-buffer Jérémy Compostella
2011-08-01 23:19 ` Antoine Levitt
2011-08-02  0:06   ` Jérémy Compostella
2011-08-02  0:40     ` Antoine Levitt
2011-08-02 12:20       ` Jérémy Compostella
2011-08-02 18:04     ` Dimitri Fontaine
2011-08-03  7:41   ` Stephen J. Turnbull
2011-08-02  0:55 ` Tim Cross
2011-08-02  1:00   ` Tim Cross
2011-08-02 12:29     ` Jérémy Compostella
2011-08-02  1:52   ` Alp Aker
2011-08-02 11:58     ` Jérémy Compostella
2011-08-02 21:55     ` Richard Stallman
2011-08-03  6:18       ` David Kastrup
2011-08-03 15:14         ` Jérémy Compostella
2011-08-04  2:24           ` Stephen J. Turnbull
2011-08-03 19:18         ` Richard Stallman
2011-08-04  6:42         ` Tim Cross [this message]
2011-08-04 14:03           ` Stefan Monnier
2011-08-04 19:56             ` Jérémy Compostella
2011-08-19  7:10       ` Leo
2011-08-14 17:16 ` Chong Yidong

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='CAC=50j-F5fcCs-OW5x2LbdaX_xCTCP9Z0SP-=pmmE5OWs=NSWA@mail.gmail.com' \
    --to=theophilusx@gmail.com \
    --cc=dak@gnu.org \
    --cc=emacs-devel@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.