public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: less.exe v481-1 cannot seek to EOF in CRLF file; current cygwin32, Win10 only.
Date: Thu, 21 Jan 2016 15:11:00 -0000	[thread overview]
Message-ID: <56A0B746.8030300@gmail.com> (raw)
In-Reply-To: <165uaTsft3776S01.1453314765@web01.cms.usa.net>

On 20/01/2016 19:32, KARL BOTTS wrote:
> In less.exe, when I use either the G or F commands on a largish CRLF file, it
> responds:

How largish ?

On Cygwin 32 bit and W7-64 I see no problem with 224 Mbytes


>     Cannot seek to that file position  (press RETURN)
>
> in the bottom "command editing line" of the display.
>
> No problem on LF-only files.  Does happen with either mintty or
> Windows-Console,
> launched from either bash or cmd.exe.
>
> Two files are attached: Karl2.cygcheck.out, which is the 'cygcheck -s -v -r'
> output,
> and LessBugMoreInfo.txt, which contains background info and some speculation.
>
> ---
> Karl Botts, kdbotts@usa.net
>

can you try to update to latest ?

You have
less                 471-1                            OK
cygwin               2.1.0-1                          OK

we are at
cygwin                                  2.4.0-1
less                                    481-1


Regards
Marco

--
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:[~2016-01-21 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 21:02 KARL BOTTS
2016-01-21 15:11 ` Marco Atzeri [this message]
2016-01-23  3:49 ` KARL BOTTS
2016-09-08 13:07   ` staffanu
2016-09-08 13:38     ` Marco Atzeri
     [not found] <190uaVPZ59120S08.1453476416@web08.cms.usa.net>
2016-01-22 18:50 ` Marco Atzeri
     [not found]   ` <20160122221927.042AA9E0.helmut.karlowski@ish.de>
2016-01-23  0:04     ` Helmut Karlowski
2016-02-02 23:57 KARL BOTTS

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=56A0B746.8030300@gmail.com \
    --to=marco.atzeri@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).