v2.2.32 release candidate released

[Timo Sirainen]

On 18 Aug 2017, at 2.25, Joseph Tam <jtam.home at gmail.com> wrote:
> 
>> a CREATE noselectbox/
>> --> With this change it's the same as CREATE "noselectbox" = will become selectable.
>> 
>> or
>> 
>> a CREATE noselectbox/childbox
>> b DELETE noselectbox/childbox
>> --> noselectbox is left behind. With this change it will be auto-deleted.
> 
> So, does that mean empty folders will be auto-deleted, or this wouldn't
> affect them?

Selectable folders won't be auto-deleted, only \NoSelect folders that have no child folders.

This auto-deletion is also done if LIST notices them. Actually the main reason it was implemented now was because with NFS if a folder is open while it's deleted, it could leave .nfs* files in the directory and prevent finishing the deletion. So a folder deletion would change it into a \NoSelect folder, but not delete it entirely. This is mainly a user-visible problem if the new ITERINDEX feature is used.