public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
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: Sat, 14 Aug 2021 12:59:23 +0900	[thread overview]
Message-ID: <20210814125923.367d7fb24ea478d95ff47a21@nifty.ne.jp> (raw)
In-Reply-To: <937c1d036e9e77c2f757e57487ad7fd5ffe84d22.camel@mindspring.com>

On Fri, 13 Aug 2021 23:46:35 -0400
C Linus Hicks <linush@mindspring.com> wrote:

> On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote:
> > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote:
> > > On Fri, 13 Aug 2021 21:47:53 -0400
> > > C Linus Hicks wrote:
> > > > 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.
> > > 
> > > 1) Does your problem also happen even if the text file contains only
> > >    ASCII chars?
> > > 2) What does 'which less' say?
> > > 3) What does 'infocmp' say?
> > > 
> > 
> > Most of the files I view have only ASCII text.
> > 
> > lhicks@ESG-Win10-1 ~
> > $ echo $TERM
> > xterm
> > 
> > lhicks@ESG-Win10-1 ~
> > $ which less
> > /usr/bin/less
> > 
> > lhicks@ESG-Win10-1 ~
> > $ infocmp
> > #       Reconstructed via infocmp from file: /usr/share/terminfo/78/xterm
> > 
> 
> I should further note that much of the time I am ssh'ed into one of several different Linux
> machines, so in that case, I would be running less from the Linux machine and displaying in the
> Cygwin xterm.
> 
> Hmmm, so now I'm starting to think the combination I have trouble with is an older less on a Linux
> machine and Cygwin xterm. I don't control what is installed on some of these Linux machines. Do you
> know if there were known issues with less, for example, the following is one that has significant
> issues:
> 
> [appldev3@ebs-app-dev3 HAF]$ less --version
> less 458 (POSIX regular expressions)
> Copyright (C) 1984-2012 Mark Nudelman
> 
> less comes with NO WARRANTY, to the extent permitted by law.
> For information about the terms of redistribution,
> see the file named README in the less distribution.
> Homepage: http://www.greenwoodsoftware.com/less

Then, could you please let us know the result of infocmp in the Linux
machine you run the less obove in cygwin xterm?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2021-08-14  3:59 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
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 [this message]
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=20210814125923.367d7fb24ea478d95ff47a21@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).