All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edgar Bonet <bonet@grenoble.cnrs.fr>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] Issue with capture of emulator output in runtime test infra
Date: Sun, 19 Sep 2021 18:59:18 +0200	[thread overview]
Message-ID: <d2a735d1-aadb-2c28-72f3-babef83448cc@grenoble.cnrs.fr> (raw)
In-Reply-To: <20210919141053.3afc7389@windsurf>

Hello!

Thomas Petazzoni wrote about support/testing/infra/emulator.py:
> the command [...] gets wrapped on two lines, like this:
>
> # curl -s -o /dev/null -w "%{http_code}\n" -X POST -H "Content-Type: application
> /json" -d '{"email": "test", "name": "test"}' http://127.0.0.1:5000

Is it just a coincidence that the line got wrapped at exactly
80 columns, or is it always at this width? 80 columns is the width of a
traditional IBM punched card, a VT100 terminal, and likely the default
for a pseudo-terminal. Does the behavior change if the width of the
pseudo-terminal ("dimensions" attribute of spawn()) is changed?

Regards,

Edgar.
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-09-19 16:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19 12:10 [Buildroot] Issue with capture of emulator output in runtime test infra Thomas Petazzoni
2021-09-19 16:59 ` Edgar Bonet [this message]
2021-09-20  8:55   ` Edgar Bonet
2021-10-04 11:55     ` Peter Korsgaard
2021-10-04 20:46       ` Edgar Bonet
2021-10-05  5:33         ` Yann E. MORIN
2021-10-05  8:54           ` Edgar Bonet
2021-10-05 16:04             ` Yann E. MORIN
2021-10-04 11:52 ` Peter Korsgaard
2021-10-04 12:14   ` Thomas Petazzoni

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=d2a735d1-aadb-2c28-72f3-babef83448cc@grenoble.cnrs.fr \
    --to=bonet@grenoble.cnrs.fr \
    --cc=buildroot@buildroot.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.
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.