On Monday, February 3, 2014 8:14:37 AM UTC+4, Ernie Rael wrote:
> I'm confused about something. With the release binary of 7.4 on
> windows, for
>
> echo exists("$xyzzy")
>
>
> the following two give different results (xyzzy is not in the
> shell's environment).
>
> xyzzy=x vim
>
> xyzzy= vim
>
>
> This would seem to indicate that ":exists" is not able to detect if
> a variable does not exist in the environment. But that's not the
> real issue.
>
>
>
> Since vim executes a wide variety of commands, it should be possible
> to unset env variables, either fixing unlet or some other mechanism.
> And coming up with a way to detect not in env, should be trivial;
> all this discussion is a spec issue.
Good to know. I have checked out `wineconsole cmd` and this is what appears:
C:\>set XXX
Environment variable XXX not defined
C:\>set XXX=1
C:\>set XXX
XXX=1
C:\>set XXX=
C:\>set XXX
Environment variable XXX not defined
. That is, setting XXX to empty is effectively unsetting variable. Wondering
what `let $XXX=''|echo exists('$XXX')|echo system('set XXX')` outputs. Maybe in
windows it is simply not possible to have empty environment variable.
--
--
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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
