diff options
| author | Peter Stephenson <pws@users.sourceforge.net> | 2006-02-07 11:29:30 +0000 |
|---|---|---|
| committer | Peter Stephenson <pws@users.sourceforge.net> | 2006-02-07 11:29:30 +0000 |
| commit | 30176eaf635a61d77114f5e834ed0684ea7dac05 (patch) | |
| tree | 344141169d7c46c58a5c74bca2b81d17862fd0ac /README | |
| parent | 90b6199e17c437408192966a3ff8266db9a4b1c2 (diff) | |
| download | zsh-30176eaf635a61d77114f5e834ed0684ea7dac05.tar.gz zsh-30176eaf635a61d77114f5e834ed0684ea7dac05.tar.xz zsh-30176eaf635a61d77114f5e834ed0684ea7dac05.zip | |
22198: do always set HOME in native emulation
Diffstat (limited to 'README')
| -rw-r--r-- | README | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/README b/README index 804d982b1..84a00706f 100644 --- a/README +++ b/README @@ -31,8 +31,9 @@ variables as an error, so can still return status 0 (depending on the handling of other arguments). This appears to be the standard shell behaviour. -The variable HOME is no longer set by the shell; it must be present -in the environment. It is valid for the variable to be unset. +The variable HOME is no longer set by the shell if zsh is emulating any +other shell at startup; it must be present in the environment or set +subsequently by the user. It is valid for the variable to be unset. Zsh has previously been lax about whether it allows octets with the top bit set to be part of a shell identifier. With --enable-multibyte set, |