From: Paul Eggert <eggert@cs.ucla.edu>
To: "Pádraig Brady" <P@draigBrady.com>, 877i7vyf3l.fsf@penguin.cs.ucla.edu
Cc: 69636@debbugs.gnu.org
Subject: bug#69636: Re: [PATCH] Improve quality of format-checking code for seq.
Date: Fri, 8 Mar 2024 11:14:00 -0800 [thread overview]
Message-ID: <c2b8d400-8693-40f2-b324-646d7258b198@cs.ucla.edu> (raw)
In-Reply-To: <c27203f4-1836-64b6-4342-7d4e6ab8a36f@draigBrady.com>
On 2024-03-08 05:47, Pádraig Brady wrote:
> seq $a | xargs printf -- 'x%.0s'
>
> printf "%${a}s" '' | tr ' ' x
>
> yes x | head -n$a | tr -d '\n'
Oh, I like those! Unfortunately the printf solution silently fails for
me when a=10000000000 due to a bug in Bash. Perhaps I'll get up the
energy to propose a fix (at least it should *noisily* fail :-).
prev parent reply other threads:[~2024-03-08 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 12:29 bug#69636: Re: [PATCH] Improve quality of format-checking code for seq User
2024-03-08 13:47 ` Pádraig Brady
2024-03-08 19:14 ` Paul Eggert [this message]
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://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2b8d400-8693-40f2-b324-646d7258b198@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=69636@debbugs.gnu.org \
--cc=877i7vyf3l.fsf@penguin.cs.ucla.edu \
--cc=P@draigBrady.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.
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).