On 8/06/11 2:38 PM, Bram Moolenaar wrote:
fabian greffrath wrote:
Am 07.06.2011 05:40, schrieb Bram Moolenaar:
This tries to expand a file pattern starting with "~/", which won't work
when $HOME isn't set. However, it should not crash.
You say the shell chokes on the command, but how does that make Vim
crash?
I don't know. Maybe it's just Windows that for some reason *believes*
that vim has crashed [1]. However, I have just tried out with another
shell, i.e. the sh.exe from UnxUtils (which is a zsh) and it works
even if both PATH and HOME are unset!
- Fabian
[1] These are the debug messages that Windows presents to me (in
German, sorry):
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: conhost.exe
Anwendungsversion: 6.1.7601.17514
Anwendungszeitstempel: 4ce79a18
Fehlermodulname: conhost.exe
Fehlermodulversion: 6.1.7601.17514
Fehlermodulzeitstempel: 4ce79a18
Ausnahmecode: c0000005
Ausnahmeoffset: 0000000000001e65
Betriebsystemversion: 6.1.7601.2.1.0.256.4
Gebietsschema-ID: 1031
Zusatzinformation 1: f7b2
Zusatzinformation 2: f7b24610852830221d2f973252451319
Zusatzinformation 3: 1131
Zusatzinformation 4: 11317911aee4606a99ac6986df83c9f2
Lesen Sie unsere Datenschutzbestimmungen online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407
Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie
unsere Datenschutzbestimmungen offline:
C:\Windows\system32\de-DE\erofflps.txt
I guess what happens is that the shell dies, and takes Vim with it.
I don't think it is up to Vim to set $HOME just to avoid the shell from
dying.
You could try running that conhost.exe without $HOME in another context,
see what happens.
Can it be reproduced without Vim? If so, a bug can be filed against the
shell. If not, perhaps we haven't fully understood it yet?
Ben.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
