From: Tim Cross <theophilusx@gmail.com>
To: "Jérémy Compostella" <jeremy.compostella@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: other-buffer advice on kill-buffer
Date: Tue, 2 Aug 2011 11:00:13 +1000 [thread overview]
Message-ID: <CAC=50j93_CnuEhf_6vAuCwe=a1HGZTzk+X8NDakFGe4JJpnfgQ@mail.gmail.com> (raw)
In-Reply-To: <CAC=50j-Bg=+sqjHv6fwgAOYQq2CfO2BfBiJX0KnL3TzxApLpxg@mail.gmail.com>
2011/8/2 Tim Cross <theophilusx@gmail.com>:
> 2011/8/2 Jérémy Compostella <jeremy.compostella@gmail.com>:
>> All,
>>
>> I'm trying to modify the behavior of the kill-buffer function to fit my
>> needs. I would like to limit the list of eligible buffers used to select
>> the buffer which will be displayed in place of the killed buffer.
>>
>> 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.
>>
>> So am I missing something ?
>> Is there a restriction on advices for C implemented function ?
>> How the kill-buffer function select the new displayed buffer ? Could I
>> really modify its behavior and how ?
>>
>
> Yes, there are some restrictions in how defadvice can be used and
> which function sit can affect. From memory, you cannot advise
> functions implemented in C, only those implemented in elisp.
>
> With respect to the buffer display, there is a current work being done
> in this area for emas 24. If you are using emacs 24, have a look at
> the buffer-display-alist thread. One of the things that was being
> asked for was examples of how the new configuration could/would be
> used. Your request may be a good test case.
>
> If your using emacs23 or earlier, personally, I would hold off until
> the emacs 24 changes have settled as you will likely have to change
> things once emacs 24 is released anyway. One of the objectives, as I
> understand it, is to make this sort of configuration easier and more
> flexible.so I expect you would be considered to be what they call an
> 'interested party'.
>
Correction - the thread you should look at is called
display-buffer-alist simplifications. Based on your subsequent
messages regarding the activity mode you have developed, I think this
thread may be even more relevant and worth checking out.
Tim
next prev parent reply other threads:[~2011-08-02 1:00 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 [this message]
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
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=50j93_CnuEhf_6vAuCwe=a1HGZTzk+X8NDakFGe4JJpnfgQ@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jeremy.compostella@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 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.