On 17/12/13 08:27, mattn wrote:
On Tuesday, December 17, 2013 1:43:20 PM UTC+9, Tony Mechelynck wrote:
On 16/12/13 12:33, mattn wrote:
You can use no-compatible mode but you can do :echo v:oldfiles.
And it refer NULL pointer.
When I start Vim (the current "Huge" version 7.4.131, without applying
your patch) with "vim -N -u NONE" then ":echo v:oldfiles" gives me a
fully populated List of files. ":oldfiles" gives the same results in a
more human-readable way.
When I start it with "vim -u NONE", thus in 'compatible' mode, the
oldfiles list is not populated (and the viminfo not used). I still
believe that this is intentional. Let's hear what Bram has to say about it.
Try:
vim -i NONE
:echo oldfiles
It should show [].
Hm, for some reason it displays the empty string instead, and
:echo v:oldfiles == []
returns 0, but
:echo empty(v:oldfiles)
returns 1 and
:echo len(v:oldfiles)
returns 0. Also,
:oldfiles
answers with
No old files
Also (to rule out the possibility of an empty value of a different
type), I tried the following:
:echo type(v:oldfiles)
which returns 3, and
:echo type(v:oldfiles) == type([])
which returns 1.
I would have expected the above results, starting at the value of
empty(), but the fact that v:oldfiles is empty without being equal to []
surprises me. Could it be a NULL pointer or something?
I get the same results in
vim -u NONE
without -N, which is not surprising.
Best regards,
Tony.
--
Reactor error - core dumped!
--
--
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.
