Timeline for Forcing buffers whose names start with "*" to be skipped in many commands?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2021 at 18:31 | vote | accept | HippoMan | ||
| Dec 8, 2021 at 23:51 | answer | added | Patience | timeline score: 2 | |
| Dec 8, 2021 at 23:36 | answer | added | HippoMan | timeline score: 1 | |
| Dec 7, 2021 at 20:44 | comment | added | HippoMan |
As an example of the complexities of this task, consider kill-buffer. After killing, it tries to present the value of (other-buffer). However, that function is defined in the emacs source file, buffer.c, and it doesn't seem to be overridable via advice.
|
|
| Dec 7, 2021 at 19:50 | comment | added | HippoMan |
There are a number of functions which utilize buffer-list, and this is what I mean by "many commands". I am trying to avoid advising each and every function which utilizes buffer-list. And it doesn't seem like buffer-list itself can be advised. This is the reason for my asking my question here.
|
|
| Dec 7, 2021 at 19:30 | review | Close votes | |||
| Dec 22, 2021 at 3:02 | |||||
| Dec 7, 2021 at 19:17 | comment | added | Drew |
You can advise individual functions that use buffers, filtering, for example, what function buffer-list returns.
|
|
| Dec 7, 2021 at 19:15 | comment | added | Drew |
Your notion of "next" buffer is not clear. It doesn't sound like you mean the buffer switched to by command next-buffer, for example. And you say, "in many commands". Please clarify what you mean.
|
|
| Dec 7, 2021 at 19:12 | comment | added | Drew | emacs.stackexchange.com/tags/elisp/info | |
| Dec 7, 2021 at 19:12 | history | edited | Drew | CC BY-SA 4.0 |
edited tags
|
| Dec 7, 2021 at 18:27 | history | asked | HippoMan | CC BY-SA 4.0 |