From: Jorgen Schaefer <forcer@forcix.cx>
To: emacs-devel@gnu.org
Subject: Why does write-region use message_with_string?
Date: Sat, 26 Oct 2013 01:27:33 +0200 [thread overview]
Message-ID: <20131026012733.5f35a2a5@forcix.kollektiv-hamburg.de> (raw)
Hi!
I'm trying to intercept all output from emacs -batch from within lisp.
This works nicely with a defadvice around `message' and `princ', except
in one case: write-region.
In fileio.c:4995, this function calls message_with_string directly,
circumventing lisp completely.
Is there a particular reason for this, or can this be replaced by the
usual message functions?
Regards,
Jorgen
next reply other threads:[~2013-10-25 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 23:27 Jorgen Schaefer [this message]
2013-10-26 1:42 ` Why does write-region use message_with_string? Stefan Monnier
2013-10-26 6:41 ` Eli Zaretskii
2013-10-26 9:16 ` Jorgen Schaefer
2013-10-28 8:02 ` Andreas Röhler
2013-10-27 22:07 ` T.V. Raman
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=20131026012733.5f35a2a5@forcix.kollektiv-hamburg.de \
--to=forcer@forcix.cx \
--cc=emacs-devel@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 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).