From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: philipk@posteo.net, emacs-devel@gnu.org, spacibba@aol.com,
juri@linkov.net
Subject: Re: Setting global variables
Date: Wed, 23 Feb 2022 23:50:16 -0500 [thread overview]
Message-ID: <E1nN652-0001aS-Iz@fencepost.gnu.org> (raw)
In-Reply-To: <jwvk0dnhx8n.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 22 Feb 2022 08:04:03 -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. ]]]
> The idea is very much like advice-add/remove but for variables instead
> of functions.
How would it work? Implementing advice is conceptually simple:
you want to asvise `foo', build a new definition for `foo'.
For variable `bar', is your ides to advise each function that uses `bar'?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-02-24 4:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220220040515.zum3iodtpscj23j3.ref@Ergus>
2022-02-20 4:05 ` About zcomplete Ergus
2022-02-20 10:12 ` Manuel Uberti
2022-02-20 10:14 ` Manuel Uberti
2022-02-20 10:54 ` Ergus
2022-02-20 12:42 ` Manuel Uberti
2022-02-20 11:11 ` Philip Kaludercic
2022-02-20 13:27 ` Ergus
2022-02-21 10:35 ` Philip Kaludercic
2022-02-21 12:22 ` Ergus
2022-02-21 15:35 ` Setting global variables (was: About zcomplete) Stefan Monnier
2022-02-21 16:57 ` Ergus
2022-02-21 23:33 ` Case Duckworth
2022-02-22 5:14 ` Richard Stallman
2022-02-22 12:35 ` Eli Zaretskii
2022-02-22 13:04 ` Setting global variables Stefan Monnier
2022-02-24 4:50 ` Richard Stallman [this message]
2022-02-25 18:01 ` Stefan Monnier
2022-02-26 4:52 ` Richard Stallman
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=E1nN652-0001aS-Iz@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=spacibba@aol.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.