Hoi.
[2020-03-22 13:17] Philipp Takacs <phil...@bureaucracy.de>
> [2020-03-22 07:20] markus schnalke <mei...@marmaro.de>
> > [2020-03-22 01:08] Philipp Takacs <phil...@bureaucracy.de>
> > > [2020-03-21 23:01] markus schnalke <mei...@marmaro.de>
> > > > [2020-03-21 17:48] Philipp Takacs <phil...@bureaucracy.de>
> > > > > [2020-03-21 10:28] markus schnalke <mei...@marmaro.de>
> > > > > >
> > > > > > - Files starting with a comma. These were backups of deleted
> > > > > > messages
> > > > > > (see the section on the trash folder in my master's thesis). Thus
> > > > > > they are considered MH files here but not further regarded. I'm
> > > > > > not sure if the code had been this way all the time, because there
> > > > > > used to the a `--with-hash-prefix' option (or similar) that
> > > > > > replaced the comma with a hash symbol as the prefix for deleted
> > > > > > messages backups. Anyways, we don't have such comma files anymore.
> > > > > > Mmh uses the trash folder for that case, i.e. we can get rid of
> > > > > > the comma prefix file handling ... possibly. Does anyone know the
> > > > > > situation in nmh: have they switched to a trash folder as well?
> > > > > > Because we're still (basically) mail storage compatible to nmh (I
> > > > > > think), we should not be fully ignorant of that situation. But we
> > > > > > could handle those backup files as `other' files.
> > > > >
> > > > > The files starting with a comma/dot aren't the problem they are
> > > > > totally
> > > > > ignored. The problem are files witch aren't totally ignored. I have a
> > > > > ugly
> > > > > workaround in the filter and I want to get rid of it.
> > > >
> > > > How I understand the situation (without looking at the code): A
> > > > folder can contain:
> > > >
> > > > - messages
> > > > - `.' and `..'
> > > > - `.mh_sequences'
> > > > - subfolders
> > > > - other files
> > > >
> > > > Other files are everything else, no matter if they are named
> > > > `.foo' or `,foo' or just `foo'.
> > > >
> > > > When we read a folder, only messages are of relevance. All the
> > > > rest is ignored.
> > >
> > > expect for the OTHERS bit set for files which aren't messages and don't
> > > start with a '.' or a ','.
> >
> > Why for files starting with a comma? Is there a sense to do that
> > in mmh? Or is it only nmh legacy/compatiblity? And still: What
> > sense does it make to ignore backup files starting with a comma,
> > if the nmh installation might be configured to use hash prefixes
> > instead of comma prefixes?
>
> I believe this is for legacy/compatiblity. The idea is, you don't have
> other files if you only have backup files in this directory.
>
> > Either we should add '#' as well or remove ','. Can you follow my
> > reasoning?
>
> For compatiblity reasons, I would say add the '#' while we have the
> other bit.
Agreed.
Please add a comment to the ',' and '#' case, as their reasons for
existance can not be found within mmh. Like:
For compatibility with nmh, ignore rmm backup files.
meillo
