From: C Linus Hicks <linush@mindspring.com>
To: cygwin@cygwin.com
Subject: Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width
Date: Fri, 13 Aug 2021 21:47:53 -0400 [thread overview]
Message-ID: <3c3a1c8172fcd73543caf9d38e49d9ca026cb1da.camel@mindspring.com> (raw)
In-Reply-To: <86bb7e63a858d60c486d7a948e168e96d98d38c8.camel@mindspring.com>
On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote:
> On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote:
> > Works Just Fine For Me!
> >
> This is Cygwin 64 on Windows 10 in a VirtualBox VM, cygcheck output attached.
>
> It has been a while since I updated Cygwin; as long as it serves my purpose, I generally don't focus
> on that; it is just a tool I use.
>
> Since I did open this thread, of course I need to make sure I am up-to-date. I have now done that
> and I don't see issues with Cygwin terminal and less, although that is not really where I am
> focusing. I mostly use xterm windows just because there are several characteristics I like about it.
>
> I am still seeing issues with xterm and less, as I stated in my original post.
>
Did I post this in the wrong list? I have not gotten a response since my update.
next prev parent reply other threads:[~2021-08-14 1:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 5:28 Display text file using less in Cygwin terminal or xterm incorrect when lines are longer then " C Linus Hicks
2021-08-07 19:33 ` Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than " Brian Inglis
2021-08-09 19:17 ` C Linus Hicks
2021-08-14 1:47 ` C Linus Hicks [this message]
2021-08-14 1:56 ` Takashi Yano
2021-08-14 2:48 ` Takashi Yano
2021-08-14 3:27 ` C Linus Hicks
2021-08-14 3:44 ` Takashi Yano
2021-08-14 3:46 ` C Linus Hicks
2021-08-14 3:59 ` Takashi Yano
2021-08-14 4:05 ` C Linus Hicks
2021-08-14 4:35 ` Takashi Yano
2021-08-14 14:31 ` C Linus Hicks
2021-08-14 4:37 ` Brian Inglis
2021-08-14 14:39 ` C Linus Hicks
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=3c3a1c8172fcd73543caf9d38e49d9ca026cb1da.camel@mindspring.com \
--to=linush@mindspring.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).