From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Console buffer width always 1 column less than setting
Date: Mon, 24 Apr 2017 07:34:00 -0000 [thread overview]
Message-ID: <58fd2606.4ca8ca0a.91abf.a636@mx.google.com> (raw)
In-Reply-To: <9484061C-4B75-43A4-8E4D-44A6D07EE4AD@solidrocksystems.com>
On Sun, 5 Feb 2017 14:12:04, Vince Rice wrote:
>> On Sun, 05 Feb 2017 11:53:16, Steven Penny wrote:
>> This issue has bothered me for some time, but I never got around to reporting
>> it. The issue is that the Cygwin buffer via Cygwin.bat is always 1 less than
>> what is set.
>> For example, the default buffer is 80 columns, same as the window size.
>> Cygwin window size is correct, but that last column can never be accessed, it
>> always stays blank and the text wraps on column 79. Here is a test:
>> 1. Enter spaces until you reach next line, this way the prompt is not adding
>> to our count
>> 2. Enter:
>> 12345678901234567890123456789012345678901234567890123456789012345678901234567890
>> Now with cmd.exe, you get all 80 characters on the same line, but with Cygwin
>> it always wraps 1 character before. I donât remember this always being the
>> case, I believe it used to work correct 1-2 years ago.
> I'm on Win7 64-bit with 64-bit Cygwin 2.6.0(0.304/5/3). To clarify, the above
> occurs with bash 4.3.46(7) in a Windows console, and I see the behavior there
> as well. This does not happen with the same bash in mintty 2.7, so it appears
> to be specific to the combination of bash and the Windows console.
http://cygwin.com/ml/cygwin/2017-02/msg00072.html
I found a fix to this problem. Create a file "cygwin-xenl.terminfo":
cygwin-xenl|cygwin eat_newline_glitch,
xenl,
use=cygwin,
Compile and install the file:
tic cygwin-xenl.terminfo
Add line to "~/.profile" or similar:
TERM=cygwin-xenl
Interestingly, if you start via the shortcut (mintty), a different terminal is
used; one that already has xenl turned on:
$ echo $TERM
xterm
$ infocmp xterm | grep xenl
am, bce, km, mc5i, mir, msgr, npc, xenl,
Running Cygwin.bat with xterm is not a solution though, because xterm uses
different values for the key codes.
http://man7.org/linux/man-pages/man5/terminfo.5.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-04-23 22:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 19:53 Steven Penny
2017-02-05 20:12 ` Vince Rice
2017-02-05 20:59 ` Steven Penny
2017-02-06 17:43 ` Lee Dilkie
2017-02-06 17:55 ` Marco Atzeri
2017-02-07 11:38 ` David Balažic
2017-02-07 14:14 ` cyg Simple
2017-02-07 15:35 ` Andrey Repin
2017-02-06 17:55 ` Vince Rice
2017-02-07 14:11 ` cyg Simple
2017-02-07 14:23 ` Lee Dilkie
2017-02-07 14:40 ` cyg Simple
2017-02-07 18:44 ` Lee Dilkie
2017-02-07 19:19 ` Steven Penny
2017-04-24 7:34 ` Steven Penny [this message]
2018-01-01 6:50 ` Steven Penny
2018-01-01 22:25 ` Steven Penny
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=58fd2606.4ca8ca0a.91abf.a636@mx.google.com \
--to=svnpenn@gmail.com \
--cc=cygwin@cygwin.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).