From: Randy MacLeod <randy.macleod@windriver.com>
To: phodina <phodina@protonmail.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Awkward line wrapping in bash
Date: Thu, 19 Sep 2019 14:45:51 -0400 [thread overview]
Message-ID: <e9a77cdd-8f1a-69d9-2d09-aed56c7d13b3@windriver.com> (raw)
In-Reply-To: <Ji28AOGAddYhx0MrDU5EjIkRSdwJCwFCsKtxE6zFAllu6lRRNxSKIJd_HoP2gWRr2U6Mkl1i-39AIVXKdnsWpiBIX40FA4DdGUqmy0zOGpA=@protonmail.com>
On 9/19/19 11:43 AM, phodina wrote:
> Hi,
>
> based on André recommendation I commented out the PS1 variable and now I get `-sh-4.4#` for the prompt. I also checked and nothing is overwriting the variable.
>
> But I tried to change the size of the shell by using `stty cols 100 rows 40` as well as different sizes (smaller and bigger than 80 columns), but the amount of characters I get on the line stays at 81 followed by carrige return. However if I record the session with `script` I get the correct amount of characters per line.
If you are able to reproduce this proble on the master, or a
stable (1) branch with one of the supported qemu or HW BSPs (2),
please open a defect in:
https://bugzilla.yoctoproject.org/
Please report the branch, what layers you are using (hopefully you
can reproduce it with just oe-core/poky + a HW layer) and
with a standard image.
../Randy
(1) https://wiki.yoctoproject.org/wiki/Releases
(2):
The list here is a good start, I'm not sure about the FSL support and
I suspect that minnow board is no longer relevant.
https://bugzilla.yoctoproject.org/describecomponents.cgi?product=BSPs
If your hardware isn't listed, and you can't reproduce the issue
in qemu or supported HW, you should contact your HW supplier.
--
# Randy MacLeod
# Wind River Linux
next prev parent reply other threads:[~2019-09-19 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 9:34 Awkward line wrapping in bash phodina
[not found] ` <8bb3f05c-966b-4076-6593-d042bb8240ad@gmail.com>
[not found] ` <6v81ntCcT70rvm2b8GwiRAeNSZSIEec-hUpr0hIN7HYR9RySExiu50vZaZM0jXSjiu2PYGbQ5mKn1e0cv3q13NlyJ5rwb6cdV0h1mpb9jXc=@protonmail.com>
2019-09-18 13:17 ` phodina
[not found] ` <bb902393-3fc3-6b68-f418-3c2a4d3b189c@gmail.com>
2019-09-19 15:43 ` phodina
2019-09-19 18:45 ` Randy MacLeod [this message]
2019-10-03 10:54 ` phodina
2019-10-03 18:43 ` Randy MacLeod
2019-09-20 1:44 ` ChenQi
2019-09-20 6:46 ` Robert Berger@yocto.user
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=e9a77cdd-8f1a-69d9-2d09-aed56c7d13b3@windriver.com \
--to=randy.macleod@windriver.com \
--cc=phodina@protonmail.com \
--cc=yocto@yoctoproject.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.