gustavo panizzo (gfa) wrote on Mon, Dec 28, 2015 at 11:58:17 +0800:
> On Sun, Dec 27, 2015 at 10:40:11PM +0000, Daniel Shahaf wrote:
> > When $HOME does not exist, asciinema fails to start.
>
> newer asciinema version, written in go, fails too but more gracefully
>
>
> gustavo-nb:(1)~$ HOME=/foo asciinema
> open /foo/.config/asciinema/config: no such file or directory
>
> if $HOME/.config exists, $HOME/.config/asciinema/config will be created.
>
>
> gustavo-nb:(1)~$ unset HOME
> gustavo-nb:~gust9547$ asciinema
> Need $HOME
>
> I don't think it is a bug, *in version 1.1.1*, in 0.9.8 (the version
> currently in the archive) it may be a bug.
I agree v1.1.1's failure mode is preferable to v0.9.8's, but I still
think it is a bug that $HOME must be set and exist. After all, if
I used the following wrapper
asciinema() {
local HOME="$(mktemp -d)" ret
command asciinema "$@"; ret=$?
rm -rf -- "$HOME"
return ret
}
everything would work just fine.
Perhaps the 'Need $HOME' error should be downgraded to a warning such as:
asciinema: warning: $HOME is not set, some features will be unavailable
Cheers,
Daniel
P.S. I think you can close #794298? I tried it in a clean jessie chroot
the other day and couldn't reproduce it.
