From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood@talktalk.net>
Cc: Alban Gruin <alban.gruin@gmail.com>,
phillip.wood@dunelm.org.uk, Michal Nowak <mnowak@startmail.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Broken interactive rebase text after some UTF-8 characters
Date: Thu, 31 Jan 2019 13:35:57 -0800 [thread overview]
Message-ID: <xmqqimy41pdu.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <2cbb5818-643d-bafd-6721-91e0d291a5fd@talktalk.net> (Phillip Wood's message of "Thu, 31 Jan 2019 20:40:43 +0000")
Phillip Wood <phillip.wood@talktalk.net> writes:
>> Are we misusing C formats?
>
> The C standard and POSIX both say that the * refers to the maximum
> number of bytes to print but it looks like it is being treated as the
> maximum number of characters on OpenIndiana.
>
> Johannes - Perhaps we should change it to use fwrite() unless printf()
> gets fixed and we're sure no other operating systems are affected?
Avoid such a rewrite, as "%*.s" that takes (int, char *) are used in
many other places in our codebase, if you can.
next prev parent reply other threads:[~2019-01-31 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 19:29 Broken interactive rebase text after some UTF-8 characters Michal Nowak
2019-01-16 10:33 ` Phillip Wood
2019-01-16 21:36 ` Michal Nowak
2019-01-17 11:04 ` Phillip Wood
2019-01-31 17:43 ` Alban Gruin
2019-01-31 20:40 ` Phillip Wood
2019-01-31 21:00 ` Alban Gruin
2019-01-31 21:35 ` Junio C Hamano [this message]
2019-02-01 7:38 ` Johannes Schindelin
2019-02-01 9:06 ` Michal Nowak
2019-02-01 14:33 ` Johannes Schindelin
2019-02-01 16:24 ` Michal Nowak
2019-02-01 17:30 ` Junio C Hamano
2019-02-01 19:00 ` Michal Nowak
2019-02-01 16:15 ` Alban Gruin
2019-02-01 16:13 ` Alban Gruin
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqimy41pdu.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=alban.gruin@gmail.com \
--cc=git@vger.kernel.org \
--cc=mnowak@startmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=phillip.wood@talktalk.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 public inbox
https://80x24.org/mirrors/git.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).