Ron Yorston

```$_``` isn't unreliable, it's just not specified in POSIX and does different things in different shells. The ```bash``` man page says: >At shell startup, set to the absolute pathname used...

The shell in busybox-w32 now respects ```$HOME``` when started with the ```-l``` option. New [prerelease](https://frippery.org/files/busybox/prerelease/) binaries are available. As has been reported before (issue #27) there's a quirk in how...

Your issue with the prompt and file name completion is the same as the one I mentioned above. The problem in this case is in the line editing library rather...

Indeed, ```lookupvar()``` is the correct way to do it, but it's a static function in ash. I've already sent a [patch](http://lists.busybox.net/pipermail/busybox/2022-March/089539.html) upstream which allows for this. It uses the equivalent...

I've make a new upstream [patch](http://lists.busybox.net/pipermail/busybox/2022-March/089540.html). Since this hasn't been applied yet I've put it on the 'tilde' branch in busybox-w32. There's a binary based on this (busybox_tilde64.exe) in the...

Actually, support for proper tilde handling is already in master. It came via upstream rather than the tilde branch. Both have the same patch. The latest [prerelease binaries](https://frippery.org/files/busybox/prerelease) have this...

- ```which``` returning the full path for ```busybox``` is a special exception: ```which busybox``` is used in the testsuite. - ```command``` adding the ```.exe``` extension is a bug which I'm...

The latest [prerelease](https://frippery.org/files/busybox/prerelease) should have a fix for the ```command -v``` issue.

>Why can't I get the path with command -v busybox? ```busybox_pre.exe``` includes a ```busybox``` applet which takes precedence over the ```busybox.exe``` binary.

Looks OK to me: ``` ~ $ ./busybox_pre sh ~ $ export PATH=".;$PATH" ~ $ which busybox.exe ./busybox.exe ~ $ command -v busybox.exe ./busybox.exe ~ $ ```