[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: HowTo: Run a hook when a buffer becomes "current"
From: |
Richard Stallman |
Subject: |
Re: HowTo: Run a hook when a buffer becomes "current" |
Date: |
Thu, 17 Dec 2015 23:04:53 -0500 |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I specifically want to run a function when a function becomes current
> and interactable by the user -- agreed that I dont want to run code in
> the case of set-buffer. For now, an after advice on select-window does
> nicely -- a select-window-hook would obviate the need for that advice
That too will cause trouble for debugging. I think it is better
for interfaces to simply operate on whatever buffer you're typing at.
What would you like to use select-window-hook to do? Let's look for
some way to achieve the ultimate goal.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
- HowTo: Run a hook when a buffer becomes "current", raman, 2015/12/16
- Re: HowTo: Run a hook when a buffer becomes "current", Nicolas Richard, 2015/12/16
- Re: HowTo: Run a hook when a buffer becomes "current", Richard Stallman, 2015/12/16
- Re: HowTo: Run a hook when a buffer becomes "current", raman, 2015/12/17
- Re: HowTo: Run a hook when a buffer becomes "current", Richard Stallman, 2015/12/18
- Re: HowTo: Run a hook when a buffer becomes "current", raman, 2015/12/19
- Re: HowTo: Run a hook when a buffer becomes "current", Dmitry Gutov, 2015/12/19
- Re: HowTo: Run a hook when a buffer becomes "current", raman, 2015/12/19
- Re: HowTo: Run a hook when a buffer becomes "current", John Wiegley, 2015/12/22
- Re: HowTo: Run a hook when a buffer becomes "current", raman, 2015/12/22
Re: HowTo: Run a hook when a buffer becomes "current", Karl Fogel, 2015/12/17