From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>
Cc: Tim Lange <mail@tim-lange.me>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Setting up editors for the GNU/GCC coding style?
Date: Mon, 1 Aug 2022 17:17:27 +0100 [thread overview]
Message-ID: <CAH6eHdRcEX6DnzjfhQ57MS7B8QeGFwGKU6mvY4b5HYt-wukR7Q@mail.gmail.com> (raw)
In-Reply-To: <YufED4DSG5U0IH7X@li-42a4824c-28a0-11b2-a85c-f55c0d5956ce.ibm.com>
On Mon, 1 Aug 2022 at 13:16, Stefan Schulze Frielinghaus wrote:
>
> On Mon, Aug 01, 2022 at 12:25:21PM +0100, Jonathan Wakely wrote:
> > On Mon, 1 Aug 2022 at 09:24, Stefan Schulze Frielinghaus wrote:
> > > I gave unexpand from GNU coreutils 8.32 a try. Looks like it cannot
> > > deal with form feeds or maybe I'm missing something?
> > >
> > > $ bash -c "printf 'foo\n\f\n bar\n'" | unexpand -
> > > foo
> > > unexpand: input line is too long
> >
> > Which linux distro are you using? I see this error on Fedora and
> > Centos 8 but not on recent Debian or Ubuntu systems.
>
> I can reproduce this on Fedora {33,34,35} and on Ubuntu 20.04 it seems
> to work.
There's a fix in Fedora rawhide now, which will also make it into
RHEL, CentOS, and (I assume) F35 and F36.
next prev parent reply other threads:[~2022-08-01 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 18:46 David Malcolm
2022-07-28 19:00 ` Alexander Monakov
2022-07-28 21:43 ` Iannetta Paul
2022-07-29 7:36 ` Marc Poulhies
2022-07-29 9:29 ` Thomas Schwinge
2022-07-29 12:34 ` Richard Earnshaw
2022-07-28 19:49 ` Tim Lange
2022-07-28 19:53 ` Jonathan Wakely
2022-08-01 8:24 ` Stefan Schulze Frielinghaus
2022-08-01 11:25 ` Jonathan Wakely
2022-08-01 12:16 ` Stefan Schulze Frielinghaus
2022-08-01 16:17 ` Jonathan Wakely [this message]
2022-08-01 10:50 ` Martin Liška
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=CAH6eHdRcEX6DnzjfhQ57MS7B8QeGFwGKU6mvY4b5HYt-wukR7Q@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mail@tim-lange.me \
--cc=stefansf@linux.ibm.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).