🚀 go-pugleaf

From article <28673@think.UUCP>, by barmar@think.COM (Barry Margolin):
> (0 size always on newly created files) 
> Multifinder doesn't continually monitor the file system.

Yes, that's evident.  But as Mf picks up file creations within a few 
seconds, surely the same signaling mechanism could be used to also inform of 
file close, so that size would also soon get set.  This does not occur, 
and it does cause confusion, as in posted example.

> (no re-sort on name change)
> I suspect this is intentional.  Suppose resorting would cause the file
> to be outside the current window

This is a more minor user problem.  But I'd think the update from 
the re-sort could be centered on the interesting file, with it's new name and
position?  This seems costless....

N'est-ce pas?

Clive