all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: (format "Hello %1$S%2$s" 'world "!")
Date: Sun, 2 Jul 2017 13:25:43 -0400	[thread overview]
Message-ID: <3ea9c72e-352e-67d6-1c85-64441d458b4a@gmail.com> (raw)
In-Reply-To: <CAM-tV--uS2iSr1-8QvpZdt_SvGpWK8dn-ebShn9BiDJ1hq=Kyg@mail.gmail.com>

On 2017-07-02 12:54, Noam Postavsky wrote:
> On Sun, Jul 2, 2017 at 12:32 PM, Clément Pit-Claudel
> <cpitclaudel@gmail.com> wrote:
>>> Why would we need a new function since %n$ would be an error for the old format anyway?
>>
>> This in itself is a good reason to have a new function.  A new function lets you migrate existing code, including plugins, to the new syntax, and load the polyfill in older Emacsen.  A new syntax that causes errors in old Emacsen isn't usable by anyone outside of Emacs core, for fear of compatibility problems.
> 
> We can still give a new name I suppose.

I think it would be nice, if we also write a polyfill. If we don't intend to write one, then there's probably no point.

>> The ones I'm familiar with use $1, {1}, or similar syntax,
> 
> What's the equivalent of %1$d in that syntax? Or is it just strings?

{1:d} (this one is Python).

>> but I've never seen %1$s :/
> 
> It's a POSIX extension to C's printf [1,2], also used by Java [3] and perl [4].
> 
> [1]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/printf.html
> [2]: https://en.wikipedia.org/wiki/Printf_format_string
> [3]: https://docs.oracle.com/javase/7/docs/api/java/util/Formatter.html
> [4]: https://perldoc.perl.org/functions/sprintf.html

Then I guess it's good enough :) Maybe I just need to get used to that syntax.

Clément.




  reply	other threads:[~2017-07-02 17:25 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
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 [this message]
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=3ea9c72e-352e-67d6-1c85-64441d458b4a@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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.