From: Uday S Reddy <uDOTsDOTreddy@cs.bham.ac.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: Redefining functions and variables
Date: Fri, 30 Jul 2010 20:32:15 +0100 [thread overview]
Message-ID: <i2v9c2$m3m$1@north.jnrs.ja.net> (raw)
In-Reply-To: <507c3b70-7530-4961-84a7-c5bfb4061831@f6g2000yqa.googlegroups.com>
On 7/29/2010 11:16 AM, Elena wrote:
> On Jul 29, 9:57 am, Stefan Monnier<monn...@iro.umontreal.ca> wrote:
>> Just as is the case for `defun', redefining macros with `defmacro'
>> is problematic. I really recommend not to do that and use defadvice
>> instead, which was designed specifically for this purpose.
>
> Do you mean macros can be adviced too? Something like this (it does
> not compile):
No, Stefan is advising you not to mess with defun or defmacro.
These are essentially fundamental built-in operations of Elisp and changing
them can produce very strange behaviors.
If you are trying to use user-contributed packages that are redefining standard
Emacs functions, then you should seriously consider whether you should use such
packages. Emacs doesn't enforce the quality of packages you use. You do.
Cheers,
Uday
next prev parent reply other threads:[~2010-07-30 19:32 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
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 [this message]
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='i2v9c2$m3m$1@north.jnrs.ja.net' \
--to=udotsdotreddy@cs.bham.ac.uk \
--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.