From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: prin1 / princ vs message ?
Date: Sun, 2 Jul 2017 08:45:58 -0400 [thread overview]
Message-ID: <CAM-tV--3bqvfnx7OyvH8VQ-oU-mNod377Uh3RUqNU_y7dtUsfw@mail.gmail.com> (raw)
In-Reply-To: <94EF128F-6A3D-41DD-B92D-0C165A4A8EB9@gmail.com>
On Sun, Jul 2, 2017 at 8:21 AM, Jean-Christophe Helary
<jean.christophe.helary@gmail.com> wrote:
>
> I am asking that because I am seeing code where standard-output is not set
> to anything but it's default (the echo area) and still prin1/princ are
> preferred over message. So, why would a developer chose prin1/princ over
> message when there is no stream argument (hence, when the output goes to
> standard output).
Using prin1/princ lets the caller let-bind standard-output to redirect
the output elsewhere, using message would not allow this.
Otherwise, I think the only practical difference is that prin1/princ
to the echo area doesn't support message coalescing, e.g.,
(progn (message "foo") (message "foo")) will show "foo [2 times]" in
*Messages*, whereas (progn (princ "foo") (princ "foo")) will show
"foofoo".
next prev parent reply other threads:[~2017-07-02 12:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 10:12 prin1 / princ vs message ? Jean-Christophe Helary
2017-07-02 11:57 ` Tino Calancha
2017-07-02 12:21 ` Jean-Christophe Helary
2017-07-02 12:32 ` Andreas Schwab
2017-07-02 12:41 ` Jean-Christophe Helary
2017-07-02 12:44 ` Tino Calancha
2017-07-02 12:45 ` Noam Postavsky [this message]
2017-07-02 13:09 ` Jean-Christophe Helary
2017-07-02 13:17 ` Noam Postavsky
2017-07-02 13:21 ` Tino Calancha
2017-07-02 13:47 ` Jean-Christophe Helary
2017-07-02 14:02 ` Jean-Christophe Helary
2017-07-02 14:23 ` Tino Calancha
2017-07-02 14:26 ` Jean-Christophe Helary
2017-07-02 14:27 ` Philipp Stephani
2017-07-02 14:38 ` Jean-Christophe Helary
2017-07-02 14:30 ` (format "Hello %1$S%2$s" 'world "!") Clément Pit-Claudel
2017-07-02 14:39 ` Jean-Christophe Helary
2017-07-02 15:03 ` Noam Postavsky
2017-07-02 16:32 ` Clément Pit-Claudel
2017-07-02 16:54 ` Noam Postavsky
2017-07-02 17:25 ` Clément Pit-Claudel
2017-12-22 21:50 ` Philipp Stephani
2017-07-02 16:56 ` Vivek Dasmohapatra
2017-12-22 21:48 ` Philipp Stephani
2017-12-22 21:44 ` Philipp Stephani
2017-07-02 14:29 ` prin1 / princ vs message ? Stefan Monnier
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=CAM-tV--3bqvfnx7OyvH8VQ-oU-mNod377Uh3RUqNU_y7dtUsfw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.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.
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.