Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Greg Minshall
Robert, et al., thanks very much. possibly mh-e could add something like a comma before integers. i'll ask and look. on the more general issue, you all know a lot more about all of this than me. but ... :) while actual bytes of memory on my laptop are semi-precious, addresses in the address sp

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread George Michaelson
I've always done sortm -verbose after big delete fests. verbose because I love watching the towers of hanoi shuffle along. lots of GUI mail systems have 'compact mailbox' command options. I assumed that everyone did periodic tidyup anyway. I'm not saying this isn't a problem. But, I seriously won

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Ken Hornstein
>a folder with the highest message number of "N" will cause the array to be >configured to support N messages, even if there are many fewer (perhaps >even one) messages No, that's not correct. If you have a single message in a folder with a count of 100, you only get one entry allocated. The

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Howard Bampton
On Thu, Mar 2, 2023 at 11:27 AM Ken Hornstein wrote: > > > This does suggest to me we should probably change the internal API > so sparse message ranges are handled better; right now all of the > programs access the folder structure members directly and assume that > there will be a msgstat struc

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Ken Hornstein
>From Ken's description above, these 111 messages would allocate almost >800,000 msgstat structures. I don't know how huge the message numbers >get in the results folder, but six digits is common. I don't recall if >I've seen seven digit or larger message numbers. I see Conrad pointed out that i

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Simon Burge
Hi Conrad, Conrad Hughes wrote: > Simon> Possibly somewhat related, Greg mentioned he uses mairix for > Simon> search. mairix produces very "sparse" results folders. > > I use mairix and have never witnessed this. A quick experiment shows > that it's because I use > > sort=date+ > > in my .ma

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Robert Elz
Date:Thu, 02 Mar 2023 13:33:01 + From:Ralph Corderoy Message-ID: <20230302133301.8900121...@orac.inputplus.co.uk> | The real issue is nmh doesn't forbid folders named with just decimal | digits and even creates them when requested. MH-E is set a bad example.

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Conrad Hughes
Simon> Possibly somewhat related, Greg mentioned he uses mairix for Simon> search. mairix produces very "sparse" results folders. I use mairix and have never witnessed this. A quick experiment shows that it's because I use sort=date+ in my .mairixrc. At a guess, the default unsorted numberi

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Simon Burge
Ken Hornstein wrote: > Exactly HOW many messages are in mhe-index? > > Ah, I think I see what's happening. That line is this: > > mp->msgstats = mh_xmalloc (MSGSTATSIZE(mp)); > > MSGSTATSIZE is defined as: > > #define MSGSTATSIZE(mp) ((mp)->num_msgstats * sizeof *(mp)->msgstats) > > num_msg

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Ralph Corderoy
Hi Ken, > > > I think we have to push this back on the MH-E people ... > >$ refile +31415 >$ folder +31415 > >31415+ has 1 message (1-1). > > I'm aware of that, but what happens if you have a subfolder that is > all numeric? I believe all of the nmh tools will treat that subfolder

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Ken Hornstein
>> I think we have to push this back on the MH-E people; Robert's >> suggestion to add a non-numeric prefix to directories it creats sounds >> like the best answer to me. > >$ refile +31415 $ folder +31415 >31415+ has 1 message (1-1). I'm aware of that, but what happens if you have a

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Ralph Corderoy
Hi, Ken wrote: > I think we have to push this back on the MH-E people; Robert's > suggestion to add a non-numeric prefix to directories it creats sounds > like the best answer to me. $ refile +31415

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Ken Hornstein
>it seems that at some point i had done a search for 74600607886815 (your >basic "magic number" :). mh-e, i guess, had created a directory with >that number as its name (it uses the search term to name subfolders >under the normal mhe-index folder). and, i guess, flist decided that >(under the ~/

Re: flist -- "Killed" -- oom (*not* 1.8 related)

2023-03-02 Thread Robert Elz
Date:Thu, 02 Mar 2023 09:49:23 +0300 From:Greg Minshall Message-ID: <814300.1677739763@archlinux> | bash archlinux (master): {49603} ls -a 74600607886815/ That would do it. | and, i guess, flist decided that | (under the ~/Mail/MHE-INDEX folder) was a message