unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sebastian Tennant <sebyte@smolny.plus.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Macro used for dynamic setting of font-lock-keywords
Date: Sun, 03 Jun 2007 12:39:48 +0300	[thread overview]
Message-ID: <874plpml5n.fsf@moley.org> (raw)
In-Reply-To: f3qosp$eib$1@sea.gmane.org

Quoth Kevin Rodgers <kevin.d.rodgers@gmail.com>:
> Sebastian Tennant wrote:
>> Quoth Xavier Maillard <xma@gnu.org>:
>>> Hi,
>>>
>>>    seem to get used as often as it probably should. I've seen people post 20+
>>>    lines of elisp to this list to do something which could be achieved more
>>>    reliably with 4 or five lines of defadvice. 
>>>
>>> Advice is considered as *dangerous* and not to be used extensively.
>>>
>> Indeed this is what I've been lead to believe.  I think RMS' position
>> on defadvice, which confirms this, is knocking about somewhere.
>
> I think RMS' position is that defadvice should not be used within Emacs
> itself.  But the inclusion of defadvice.el in Emacs is tacit
> acknowledgement of its usefulness: When there is no variable or hook
> function that the user can customize to achieve some new behavior,
> defadvice allows you to modify the behavior of a function _without
> duplicating its original definition in its entirety_.  Thus you can
> write a very small piece of code that is *more* likely to continue
> to work over time, even as the implementation of the underlying function
> evolves within Emacs, and in conjunction with other customizations of
> the function.  That makes it *less* dangerous than the naive approach of
> copy-and-paste.

Ah.  Everything is illuminated.

Many thanks.

Sebastian

  parent reply	other threads:[~2007-06-03  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1240.1180113798.32220.help-gnu-emacs@gnu.org>
2007-05-26  8:20 ` Macro used for dynamic setting of font-lock-keywords Tim X
2007-05-26 10:40   ` Sebastian Tennant
     [not found]   ` <mailman.1274.1180175941.32220.help-gnu-emacs@gnu.org>
2007-05-26 15:23     ` Tim X
2007-05-26 20:07       ` Sebastian Tennant
2007-06-02  3:29         ` Kevin Rodgers
     [not found]       ` <mailman.1303.1180209955.32220.help-gnu-emacs@gnu.org>
2007-05-27  3:30         ` Tim X
2007-05-27 21:45           ` Xavier Maillard
2007-05-28  9:22             ` Sebastian Tennant
2007-06-02  3:41               ` Kevin Rodgers
2007-06-02  7:26                 ` Eli Zaretskii
2007-06-03  9:39                 ` Sebastian Tennant [this message]
     [not found]           ` <mailman.1339.1180303291.32220.help-gnu-emacs@gnu.org>
2007-05-28  8:37             ` Tim X
2007-06-10  0:51 ` Stefan Monnier
2007-05-25 17:24 Sebastian Tennant

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=874plpml5n.fsf@moley.org \
    --to=sebyte@smolny.plus.com \
    --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.
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).