public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: John S Cooper <John.Cooper@eu.citrix.com>
To: earnie_boyd@yahoo.com
Cc: John S Cooper <John.Cooper@eu.citrix.com>, cygwin@sourceware.cygnus.com
Subject: Re: problems with less
Date: Wed, 26 Apr 2000 06:28:00 -0000	[thread overview]
Message-ID: <u8zy1m1v3.fsf@KONTIKI.cam.eu.citrix.com> (raw)
In-Reply-To: <20000426125833.21415.qmail@web114.yahoomail.com>

Earnie Boyd <earnie_boyd@yahoo.com> writes:

 > > Since upgrading to cygwin 1.0 (on Win2K) less no longer displays properly.
 > 
 > Is that cygwin 1.0.0 or cygwin 1.1.0?  The difference is that the cygwin 1.0.0
 > is the CD version and the cygwin 1.1.0 is the net release.

I pulled it off the net, so it must be 1.1.0.

 > > When I `less c:/etc/termcap', the top 3 lines of the file are not shown, even
 > > after typing `g' (start of file).  However, if I type 'G' (end of file)
 > > followed by 'g' then it is shown, although searching for strings doesn't
 > > display the highlighted matches (they seem to be off the top of the screen).
 > > It's pretty much unusable really.
 > 
 > I just tried thist using NT4 sp4, cygwin 1.1.0 and there wasn't a problem.
 > I saw the head of the file, the tail of the file and even the hightlighted
 > search strings.  BTW, the Command window is set for 2500 lines of buffer
 > with 50 lines of display.


Hmm.  I am using Win2K if that makes any difference.  It seems that the display
is always messed up for me when the file being viewed has lines that wrap
(i.e., longer than $COLUMNS, which is 80 for me).  I don't use a horizontal
scrollbar.

If I pipe a file with the majority of its lines longer than 80 characters I get
an extra newline everywhere a lines wraps, and after `G' `g', I can no longer
view the top of the buffer.  Same behavior when running under bash (as opposed
to zsh, my preferred shell).

The B20.1 `less' doesn't exhibit this behavior.  In fact, I've just discovered
that display problems with my B20.1 less only show up when I provide the -r
option.  I guess I'll revert to the B20.1 version for now...

Please Cc me on any replies as I'm not a member of the list.

    --- John


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-04-26  6:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-26  5:59 Earnie Boyd
2000-04-26  6:28 ` John S Cooper [this message]
     [not found] <Earnie>
     [not found] ` <Boyd's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <"Wed,>
     [not found]         ` <26>
     [not found]           ` <Apr>
     [not found]             ` <2000>
     [not found]               ` <05:58:33>
     [not found]                 ` <-0700>
     [not found]                   ` <(PDT)>
2000-04-26  6:56                     ` Michael Hirmke
2000-05-09  7:42                       ` John S Cooper
2000-05-09  9:08                         ` Chris Faylor
2000-05-09 10:25                           ` Bob McGowan
  -- strict thread matches above, loose matches on Subject: below --
2000-04-26  6:48 Earnie Boyd
2000-04-26  3:26 John S Cooper
2000-04-26  8:27 ` Tim Prince
2000-04-27  7:17   ` John S Cooper
2000-04-27  7:23     ` Charles S. Wilson

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=u8zy1m1v3.fsf@KONTIKI.cam.eu.citrix.com \
    --to=john.cooper@eu.citrix.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=earnie_boyd@yahoo.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).