On 14 Oct, Jim Lesurf wrote:
The other key point is to check first if there is anything in the
existing !RamScrap that needs to be kept because an application is
treating what should be an area for *scrap* as a place to hold permanent
info. IIRC !NetSurf does this.
That means you can then delete any genuine scrap to reduce the size of
what it copied. But by default the main change as a result of doing the
above is that any 'new' scrap files will be lost over the next
shutdown-startup cycle. However so far as I'm concerned that is what
*should* occur with real 'scrap' files.
