[Libguestfs] [PATCH 1/7] fish: Do not emit error message if history file cannot be open for writing.

Hilko Bengen bengen at hilluzination.de
Fri Jan 20 12:06:53 UTC 2012


* Jim Meyering:

> What is the motivation for this change?

I noticed this error message because sbuild built the package with HOME
set to a non-existing directory which caused a test script to fail.

> Wouldn't you want to be alerted if this were due to EACCES, EPERM or EIO?

Not being able to save history isn't really a critical error, as far as
I'm concerned.

I have tried some other programs how they handle this situation (bash,
sqlite3). None of them complained when they couldn't save their command
history.

-Hilko




More information about the Libguestfs mailing list