Re: [9front] rio consctl behaviour

[Silas McCroskey <inkswinc@gmail.com>]

> > I don't see much issue with /rc/bin/hold, other than that it blanks
> > the file on-disk until you exit hold mode, which can lead to
> > surprising problems if you e.g. just close the window without exiting
> > hold mode.
>
> what surprising problems are those? i'm not able to imagine right now

/bin/hold an existing file with contents (not ones you care to keep),
then delete the window (or shut down, end your drawterm session,
whatever) without exiting hold mode.

The file will be left blank, because >path/to/file within the script
truncated it at the *start* of the process, rather than doing
truncate-and-write at the end. No way to retrieve the original other
than to pull it from dump.

I encountered this when I set up a "notes" window in each of my
sub-rios (most of which usually won't have edits in a given session)
and they kept getting lost on session close. I've switched to sam -d
for that (a better choice anyways) and haven't looked back.

Perhaps a more reasonable choice for hold would be to write to a temp
file path and then mv it after completion.

- sam-d