[bug #46815] problem when testing file size

2024-05-26 Thread James Youngman
Update of bug #46815 (group findutils): Status: Need Info => None ___ Reply to this item at: ___ Mess

[bug #46815] problem when testing file size

2018-09-23 Thread James Youngman
Follow-up Comment #8, bug #46815 (project findutils): The existing behaviour is user-surprising. POSIX specifies nly (IIRC) the rouding behaviour when dealing with sizes lacking a suffix (i.e. implicitly, blocks). GNU find's current behaviour generalizes this rounding behaviour, but many people

[bug #46815] problem when testing file size

2018-09-06 Thread anonymous
Follow-up Comment #7, bug #46815 (project findutils): I'm a decades-long professional programmer, and even I just found the present behavior of rounding up very surprising, which is why I'm here posting. If I can get confused, an ordinary user has no chance, and may well miss the fact that the da

[bug #46815] problem when testing file size

2016-04-25 Thread Dale Worley
Follow-up Comment #6, bug #46815 (project findutils): There's no strong reason to add -filesize N because -size Nc has the same effect. The major reason would be if -size Nc is just too complicated for an ordinary user to figure out. ___

[bug #46815] problem when testing file size

2016-04-23 Thread xyz dragon
Follow-up Comment #5, bug #46815 (project findutils): I also find this very counter-intuitive. A -filesize instead of -size sounds ok to me it it is documented well. Even if -size was documented well, I don't think it should behave like this without providing an alternative like -filesize, but tha

Re: [bug #46815] problem when testing file size

2016-01-13 Thread Martin Steigerwald
Am Sonntag, 10. Januar 2016, 22:43:00 CET schrieb James Youngman: > On Sun, Jan 10, 2016 at 7:23 PM, Bernhard Voelker > wrote: > > On 01/09/2016 04:41 PM, James Youngman wrote: > >> Let's re-open the discussion about what to call the "sane" alternative to > >> -size, and implement it this time. >

Re: [bug #46815] problem when testing file size

2016-01-13 Thread Martin Steigerwald
Am Montag, 11. Januar 2016, 02:29:24 CET schrieb Bernhard Voelker: > On 01/11/2016 12:43 AM, Assaf Gordon wrote: > >> Suppose someone wants to find files smaller than 20MiB. Are you sure > >> that the best answer we should give them is that they should use > >> "find -size -20971520c"? > > Altho

Re: [bug #46815] problem when testing file size

2016-01-10 Thread Bernhard Voelker
On 01/11/2016 12:43 AM, Assaf Gordon wrote: >> Suppose someone wants to find files smaller than 20MiB. Are you sure >> that the best answer we should give them is that they should use >> "find -size -20971520c"? Although this is inconvenient, there are several ways for the user to avoid doing the

Re: [bug #46815] problem when testing file size

2016-01-10 Thread Assaf Gordon
Hello all, > On Jan 10, 2016, at 17:43, James Youngman wrote: > > On Sun, Jan 10, 2016 at 7:23 PM, Bernhard Voelker > wrote: >> On 01/09/2016 04:41 PM, James Youngman wrote: >>> Let's re-open the discussion about what to call the "sane" alternative to >>> -size, and implement it this time. [...

Re: [bug #46815] problem when testing file size

2016-01-10 Thread James Youngman
On Sun, Jan 10, 2016 at 7:23 PM, Bernhard Voelker wrote: > On 01/09/2016 04:41 PM, James Youngman wrote: >> Let's re-open the discussion about what to call the "sane" alternative to >> -size, and implement it this time. > > I'm not so enthusiastic, [...] > I'd rather suggest to re-work the --help

Re: [bug #46815] problem when testing file size

2016-01-10 Thread Bernhard Voelker
On 01/09/2016 04:41 PM, James Youngman wrote: > Let's re-open the discussion about what to call the "sane" alternative to > -size, and implement it this time. I'm not so enthusiastic, i.e., only 20:80 for adding such a -filesize option. The question is: what functionality would it provide which co

[bug #46815] problem when testing file size

2016-01-09 Thread James Youngman
Update of bug #46815 (project findutils): Status: Invalid => Need Info Open/Closed: Closed => Open ___ Follow-up Comment #4: Yes, both Sebasti

[bug #46815] problem when testing file size

2016-01-08 Thread Dale Worley
Follow-up Comment #3, bug #46815 (project findutils): I have a very strong suspicion that the current code behaves "correctly", that is, in the way that "find" has always worked. The original -size meaning "Does the file occupy N (512-byte) disk blocks?". (Of course, usually people would use "-s

[bug #46815] problem when testing file size

2016-01-07 Thread anonymous
Follow-up Comment #2, bug #46815 (project findutils): Hi James, Thanks for your quick response! Before I decided to submit this report I checked out the current version of GNU findutils as recommended on the project's website. The code for comparing file sizes, which I've quoted in the report, i

[bug #46815] problem when testing file size

2016-01-05 Thread James Youngman
Update of bug #46815 (project findutils): Category:find => documentation Status:None => Invalid Assigned to:None => jay Open/Closed:

[bug #46815] problem when testing file size

2016-01-04 Thread anonymous
URL: Summary: problem when testing file size Project: findutils Submitted by: None Submitted on: Di 05 Jan 2016 06:08:51 UTC Category: find Severity: 3 - Normal