unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alp Aker <alptekin.aker@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: "Jérémy Compostella" <jeremy.compostella@gmail.com>, emacs-devel@gnu.org
Subject: Re: other-buffer advice on kill-buffer
Date: Mon, 1 Aug 2011 21:52:18 -0400	[thread overview]
Message-ID: <CACxch4qqiipnBRaunAqf5hrG=5ddbOUpNx73vDwsMThUehdwww@mail.gmail.com> (raw)
In-Reply-To: <CAC=50j-Bg=+sqjHv6fwgAOYQq2CfO2BfBiJX0KnL3TzxApLpxg@mail.gmail.com>

Tim Cross wrote:

> From memory, you cannot advise functions implemented in C, only those
> implemented in elisp.

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.

Jérémy Compostella wrote:

>> I have tried to advice the other-buffer function which seems called
>> (Cf. buffer.c) but my advice is never called in this case. Indeed, my
>> other-buffer advice is correctly called on switch-to-buffer call but
>> never on kill-buffer call.

Are you sure your advice on other-buffer is being called when
switch-to-buffer is called?  That shouldn't be possible, as switch-to-buffer
is a primitive, like kill-buffer; neither should see your advice.



  parent reply	other threads:[~2011-08-02  1:52 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 [this message]
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
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

  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='CACxch4qqiipnBRaunAqf5hrG=5ddbOUpNx73vDwsMThUehdwww@mail.gmail.com' \
    --to=alptekin.aker@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jeremy.compostella@gmail.com \
    --cc=theophilusx@gmail.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).