<!-- The comments between these brackets won't show up in the submitted issue (as you can see in the Preview). -->


<!-- Please try to download latest, https://github.com/schollz/croc/releases/latest of croc before reporting a bug! -->

## Describe the bug
<-- A clear and concise description of what the bug is. -->
Croc fail to run with the following error if `HOME` env var is not defined
```
[error] 2024/03/27 08:19:11 cli.go:448: $HOME is not defined
2024/03/27 08:19:11 $HOME is not defined
```

## To Reproduce
Steps to reproduce the behavior:
```
$ HOME= ./croc
[error] 2024/03/27 08:19:11 cli.go:448: $HOME is not defined
2024/03/27 08:19:11 $HOME is not defined
```
<-- 1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error -->

## Expected behaviour
<-- A clear and concise description of what you expected to happen. -->
Croc should run normally

## Version
<-- Check "croc -v" and report it -->
```
$ ./croc -v                                                          
croc version v9.6.14
```

## Additional context
I tried to run Croc on hardened OS and embedded device where `HOME` is not defined to prevent creation of user config files. Croc fails to run with the above error. I have to manually define the `HOME` env to run Croc, like `HOME=/tmp ./croc`. It would be great if Croc doesn't require `HOME` env var, like a portable executable that doesn't create any file on the host machine.



Croc fail to run when HOME env var is not defined
This is a GitHub Issue
repo:croc
owner:schollz
Title : Croc fail to run when HOME env var is not defined
Issue date:

--- start body ---
<!-- The comments between these brackets won't show up in the submitted issue (as you can see in the Preview). -->


<!-- Please try to download latest, https://github.com/schollz/croc/releases/latest of croc before reporting a bug! -->

## Describe the bug
<-- A clear and concise description of what the bug is. -->
Croc fail to run with the following error if `HOME` env var is not defined
```
[error] 2024/03/27 08:19:11 cli.go:448: $HOME is not defined
2024/03/27 08:19:11 $HOME is not defined
```

## To Reproduce
Steps to reproduce the behavior:
```
$ HOME= ./croc
[error] 2024/03/27 08:19:11 cli.go:448: $HOME is not defined
2024/03/27 08:19:11 $HOME is not defined
```
<-- 1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error -->

## Expected behaviour
<-- A clear and concise description of what you expected to happen. -->
Croc should run normally

## Version
<-- Check "croc -v" and report it -->
```
$ ./croc -v                                                          
croc version v9.6.14
```

## Additional context
I tried to run Croc on hardened OS and embedded device where `HOME` is not defined to prevent creation of user config files. Croc fails to run with the above error. I have to manually define the `HOME` env to run Croc, like `HOME=/tmp ./croc`. It would be great if Croc doesn't require `HOME` env var, like a portable executable that doesn't create any file on the host machine.



--- end body ---

None