From: L A Walsh <cygwin@tlinx.org>
To: jp <jpcleev@yahoo.fr>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Prompt wrapping lines problems
Date: Sat, 09 Oct 2021 06:41:53 -0700 [thread overview]
Message-ID: <61619C21.2030809@tlinx.org> (raw)
In-Reply-To: <919866450.1283857.1633765090246@mail.yahoo.com>
On 2021/10/09 00:38, jp wrote:
>
>
> I'm very happy that you respond me. Yes, I've tried the solution
> suggested but I didn't succeed, but it doesn't matter now, because I've
> installed and old version of cygwin.
>
> Theese are the result of the command, but it will not help you because
> it comes from the old version of cygwin and not from the new one
> containing the bug.
>
>
> $ echo "$TERM"
> xterm
>
> me@me ~
> $ stty -a
> speed 38400 baud; rows 22; columns 191; line = 0;
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>^^^>...That's awfully wide!!!
normally you use 80 charcaters wide -- and the terminal you showed looked
more like 80 characters, than 191.
Bash may not be wrapping until 191,
try setting columns to 80 (stty cols 80)
and making sure your stty -a shows the same columns
as your '$LINES' variable.
About COLUMNS, I see:
COLUMNS
Used by the select compound command to determine the terminal
width when printing selection lists. Automatically set if the
checkwinsize option is enabled or in an interactive shell upon
receipt of a SIGWINCH.
----
This suggests that it might be necessary to have the checkwinsize
variable set, since if you change the size of your bash window, it won't
have anyway of knowing if that option is off
prev parent reply other threads:[~2021-10-09 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1138844908.4160788.1633516517585.ref@mail.yahoo.com>
2021-10-06 10:35 ` jp
2021-10-08 23:39 ` L A Walsh
[not found] ` <919866450.1283857.1633765090246@mail.yahoo.com>
2021-10-09 13:41 ` L A Walsh [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61619C21.2030809@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=jpcleev@yahoo.fr \
/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).