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, 08 Sep 2016 13:38:00 -0000	[thread overview]
Message-ID: <7ab230d4-17a7-56d1-b3e0-e418166f1747@gmail.com> (raw)
In-Reply-To: <1473340019198-129864.post@n5.nabble.com>

On 08/09/2016 15:06, staffanu wrote:
> KARL BOTTS wrote
>>> ---------------------------------------------------
>>>>> Any size larger than a few meg.  That is, any size that takes more
>>> than
>> a few
>>>>> milliseconds to seek to the end, I think.
>>>>
>>>> We will need someone with W10 to test it and confirm it.
>>>> On W7 I have no issue at all with 250MB file
>>>
>>> Tested on W10-64-cygwin-32 and a 207M-file, dos and unix-endings: both
>>> behave the same, i.e. no error when pressing 'G' and display the last
>>> line. Was that the question?
>>>
>>> cygwin 2.2.1, less 481
>>>
>>> -Helmut
>>
>> I have reproduced on Win7, same exact cygwin, same exact symptom.
>>
>> OK, that you guys can't reproduce suggests that there is something special
>> about my cygwin installation.
>>
>> What is special, I suspect, is that I have not actually recreated it in
>> many
>> years: I just update it, and copy the whole thing from machine to machine.
>> (I
>> described this in the attachment to my original email.)  That has worked
>> well
>> for a long time -- it is much easier and more consistent than running
>> setup.exe on many machines.  But I suspect it has broken down.  Somehow, I
>> may
>> have old libs or old config files mixed with new.  (This last update, from
>> 1.7
>> to 2.3, is clearly a big one.)
>>
>> So, I will re-install cygwin from scratch on one machine, this weekend.
>>
>> In the meantime, put this bug report on hold.  Thanks to all of you.
>>
>> I will let the list know how this comes out.
>
> Was this ever resolved? I have, I guess, the same problem. I cannot see that
> the size of files matter, however -- I see the problem for all CRLF files
> that I tested. (It worked fine before upgrading a few days ago.)
>
> The weird thing is that, moving the file with CRLF line endings to a binary
> mounted filesystem makes less work just fine. Reading the file from a text
> mounted filesystem results in the problem. Is not the point with text mounts
> to be able to read text files with CRLF line endings?
>
> Just as Karl, my Cygwin installation is very old -- i.e., any registry
> entries (that I think might include mount options?) might have been written
> 10 years ago. Did the meaning of text/binary mounts change?
>
> Staffan
>


no change on less package, if you are asking it.
So I expect no change on the matter.

In general, I do not see the added value of a text mount.

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-09-08 13:38 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
2016-01-23  3:49 ` KARL BOTTS
2016-09-08 13:07   ` staffanu
2016-09-08 13:38     ` Marco Atzeri [this message]
     [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=7ab230d4-17a7-56d1-b3e0-e418166f1747@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).