all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: prin1 / princ vs message ?
Date: Sun, 2 Jul 2017 21:21:47 +0900	[thread overview]
Message-ID: <94EF128F-6A3D-41DD-B92D-0C165A4A8EB9@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1707022055560.13347@calancha-pc>

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


> On Jul 2, 2017, at 20:57, Tino Calancha <tino.calancha@gmail.com> 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")

Tino,

I think that was pretty clear that I had actually read the documentation about prin1, princ and message. So let me reiterate:

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).

The documentation seems to imply that message should be preferred, but are there cases where prin1/princ are the best choice ?

Jean-Christophe 

[-- Attachment #2: Type: text/html, Size: 8244 bytes --]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=94EF128F-6A3D-41DD-B92D-0C165A4A8EB9@gmail.com \
    --to=jean.christophe.helary@gmail.com \
    --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 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.