unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: How to automatically write *Messages" buffer to a file?
Date: Wed, 24 Nov 2004 14:19:16 -0800	[thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBGENBCJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <jwvvfbvasfn.fsf-monnier+gnu.emacs.help@gnu.org>

Something that I don't like about advised functions is that I cannot use the
debugger with them (unless I'm missing something). - Drew

   Stefan's "advice" advice:

    `advice' is a sledghammer: it's the last resort before
    modifying the source code.

    Advising is a source of major headaches because of unexpected
    interactions with other pieces of code...
    Advice have to be written *extremely* carefully.
    I.e. if you can do it without `advice', then don't use `advice'.

  parent reply	other threads:[~2004-11-24 22:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1150.1101268518.27204.help-gnu-emacs@gnu.org>
2004-11-24 14:06 ` How to automatically write *Messages" buffer to a file? Pascal Bourguignon
2004-11-24 15:52   ` Eli Zaretskii
2004-11-24 19:01     ` Joe Corneli
     [not found]     ` <mailman.1295.1101323448.27204.help-gnu-emacs@gnu.org>
2004-11-24 20:16       ` Stefan Monnier
2004-11-24 20:28         ` Joe Corneli
     [not found]         ` <mailman.1305.1101328729.27204.help-gnu-emacs@gnu.org>
2004-11-24 20:55           ` Stefan Monnier
2004-11-24 21:52             ` Joe Corneli
2004-11-24 22:19             ` Drew Adams [this message]
2004-11-25  4:56             ` Joe Corneli
     [not found]             ` <mailman.1370.1101359173.27204.help-gnu-emacs@gnu.org>
2004-11-25 20:20               ` Stefan Monnier
2004-11-24 22:00           ` Thien-Thi Nguyen
2004-11-25  4:52             ` Joe Corneli
2004-12-01 19:08 ` Kevin Rodgers
2004-11-24  3:43 Brad Collins

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=FDELKNEBLPKKDCEBEJCBGENBCJAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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. 
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).