From: Richard Stallman <rms@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: npostavs@users.sourceforge.net, emacs-devel@gnu.org, dgutov@yandex.ru
Subject: Re: [PATCH] RFC: eldoc-documentation-functions hook
Date: Mon, 13 Jun 2016 16:36:05 -0400 [thread overview]
Message-ID: <E1bCYab-0002tF-Ud@fencepost.gnu.org> (raw)
In-Reply-To: <20160612194452.GA12853@holos.localdomain> (message from Mark Oteiza on Sun, 12 Jun 2016 15:44:52 -0400)
[[[ 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. ]]]
It is asking for trouble to have anything in the Emacs sources
put advice onto any function, because it interferes with debugging.
If you see a call to function foo, which has advice on it, you will be
perplexed why its behavior does not match its source.
(If you wrote the advice, you won't have this problem if you remember
that you put the advice on.)
A hook is cleaner, because the call to run-hooks in the source code of
foo informs you that you should check what hook functions there are.
Thus, I ask people to take care not to install anything in the Emacs
sources which creates advice -- and to replace any existing advice
with hooks.
--
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.
next prev parent reply other threads:[~2016-06-13 20:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 6:12 [PATCH] RFC: eldoc-documentation-functions hook Mark Oteiza
2016-06-12 7:09 ` Eli Zaretskii
2016-06-12 7:46 ` Leo Liu
2016-06-12 8:33 ` Eli Zaretskii
2016-06-12 18:24 ` Mark Oteiza
2016-06-13 21:17 ` Mark Oteiza
2016-06-17 21:08 ` [PATCH v3] " Mark Oteiza
2016-07-07 3:30 ` Mark Oteiza
2016-07-07 4:12 ` Leo Liu
2016-07-07 10:02 ` Kaushal Modi
2016-07-17 15:17 ` Noam Postavsky
2016-07-17 17:48 ` Mark Oteiza
2016-07-17 23:47 ` Dmitry Gutov
2016-07-18 0:09 ` Leo Liu
2016-07-17 18:28 ` Stefan Monnier
2016-07-17 18:52 ` Stefan Monnier
2016-07-18 21:27 ` Mark Oteiza
2016-07-19 2:47 ` Stefan Monnier
2016-07-19 23:20 ` Mark Oteiza
2016-07-20 1:50 ` Clément Pit--Claudel
2016-07-20 4:50 ` John Wiegley
2016-07-20 23:03 ` Mark Oteiza
2016-07-07 14:55 ` Clément Pit--Claudel
2016-06-12 13:23 ` [PATCH] " Noam Postavsky
2016-06-12 18:52 ` Mark Oteiza
2016-06-12 18:57 ` Dmitry Gutov
2016-06-12 19:44 ` Mark Oteiza
2016-06-12 19:50 ` Dmitry Gutov
2016-06-13 20:36 ` Richard Stallman [this message]
2016-06-19 2:45 ` Dmitry Gutov
2016-06-20 23:00 ` Richard Stallman
2016-06-13 4:37 ` Leo Liu
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=E1bCYab-0002tF-Ud@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
--cc=npostavs@users.sourceforge.net \
/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).