From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Redefining functions and variables
Date: Tue, 27 Jul 2010 22:21:17 +0200 [thread overview]
Message-ID: <jwvocdsk79w.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 68e690c9-aece-461d-afe9-ca9115ceaee5@m1g2000vbh.googlegroups.com
> I've noticed that some user contributed packages redefine standard
> functions or variables.
That's usually a bad idea. The better way to do it is via defadvice,
which lets you do it in a way that keeps track of the presence of such
a change and knows how to combine multiple such changes.
> I wonder whether there is a way to catch such redefinitions whenever
> they happen (which also would help when accidentally redefining
> something)
Not sure what you mean by that. I guess that means "no".
> Moreover, I wonder whether redefining a function by means of "defun"
> gets same results as assigning a new function to a symbol using
> "fset".
Mostly, yes. But defun keeps track of the file where the defun happened
(for things like C-h f), whereas fset doesn't do any such thing.
Stefan
next prev parent reply other threads:[~2010-07-27 20:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 15:12 Redefining functions and variables Elena
2010-07-27 20:21 ` Stefan Monnier [this message]
2010-07-27 22:16 ` Elena
2010-07-28 0:35 ` Andreas Politz
2010-07-28 7:51 ` Elena
2010-07-28 14:29 ` Elena
2010-07-28 18:48 ` Andreas Politz
2010-07-28 20:37 ` Pascal J. Bourguignon
2010-07-29 8:32 ` Elena
2010-07-29 9:57 ` Stefan Monnier
2010-07-29 10:16 ` Elena
2010-07-29 13:14 ` Stefan Monnier
2010-07-30 19:32 ` Uday S Reddy
2010-07-29 10:31 ` Andreas Politz
2010-07-29 11:46 ` Johan Bockgård
2010-07-29 15:54 ` Andreas Politz
2010-07-29 12:41 ` Tim X
2010-07-29 10:03 ` Pascal J. Bourguignon
2010-07-29 10:28 ` Elena
2010-07-29 20:35 ` Johan Bockgård
2010-07-29 22:22 ` Tim X
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=jwvocdsk79w.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
/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.