From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Console buffer width always 1 column less than setting
Date: Mon, 01 Jan 2018 06:50:00 -0000 [thread overview]
Message-ID: <5a49da2a.74109d0a.82d07.8291@mx.google.com> (raw)
In-Reply-To: <58fd2606.4ca8ca0a.91abf.a636@mx.google.com>
On Sun, 23 Apr 2017 15:09:10, Steven Penny wrote:
> 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
http://cygwin.com/ml/cygwin/2017-04/msg00297.html
to any who might have used this solution - i discovered a bad side effect
when searching man pages, if you use the "/" operator - the first matching line
is removed, and you are brought to the following line - then if you try to
scroll up - the previous lines are there but not the matching line
subsequent matching lines are shown as expected - this is for my custom terminal
above and any terminal using "xenl" - not sure what a workaround for this is
other than dont use "xenl" and deal with the missing column per the original
issue.
--
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:[~2018-01-01 6:50 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
2018-01-01 6:50 ` Steven Penny [this message]
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=5a49da2a.74109d0a.82d07.8291@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).