unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
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 20:57:10 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1707022055560.13347@calancha-pc> (raw)
In-Reply-To: <061782A1-0A51-49A1-9AA4-706AF8927D01@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]



On Sun, 2 Jul 2017, Jean-Christophe Helary wrote:

> What's the difference between:
>
> (let ((name "JC"))
>  (prin1 "My name ")
>  (princ " is ")
>  (princ name)
>  (princ ".\n\n"))
>
> and
>
> (message "My name is %s.\n\n" "JC")
>
> ?
>
> Unless we have a non default value for standard-output both send the value to the echo area, right ?
>
> Besides for the possibility prin1 and princ have of printing to standard-output and not specifically to the echo area, what is the actual difference between the two and message ?

* Documentation about prin? family:
(info "(elisp) Output Functions")

* "The recommended way to show a message in the echo area is with the
   `message' function, not `princ’".
   Extracted from:
(info "(elisp) Programming Tips")

* `message' and the echo area:
(info "(elisp) The Echo Area")

  reply	other threads:[~2017-07-02 11:57 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 [this message]
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
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

  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=alpine.DEB.2.20.1707022055560.13347@calancha-pc \
    --to=tino.calancha@gmail.com \
    --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 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).