This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Console buffer width always 1 column less than setting


> On Feb 5, 2017, at 1:53 PM, Steven Penny <svnpenn@gmail.com> 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.


--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]