public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Vince Rice <vrice@solidrocksystems.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Console buffer width always 1 column less than setting
Date: Sun, 05 Feb 2017 20:12:00 -0000	[thread overview]
Message-ID: <9484061C-4B75-43A4-8E4D-44A6D07EE4AD@solidrocksystems.com> (raw)
In-Reply-To: <589782ac.ac3f9d0a.4d8a7.f181@mx.google.com>

> 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

  reply	other threads:[~2017-02-05 20:12 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 [this message]
2017-02-05 20:59   ` Steven Penny
2017-02-06 17:43     ` Lee Dilkie
2017-02-06 17:55       ` Vince Rice
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-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
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=9484061C-4B75-43A4-8E4D-44A6D07EE4AD@solidrocksystems.com \
    --to=vrice@solidrocksystems.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).