Jason Franklin wrote:
> Just a follow up on what I've learned here.
>
> I don't think that the ":file" command makes much sense in the cmdline window.
> However, I don't think it should be disallowed when curbuf_lock is set. Since
> these restrictions go together, not much can be done.
>
> Still, this is more of a decision about when it is okay to call the ":file"
> command. It's not a bug. Since I was concerned with the output of ":file"
> only, I used the following...
>
> :execute "normal! \<C-G>"
>
> instead. That worked for me!
>
> Just a note for anyone who may have read my original post.
Not sure what you are actually discussing here. I can use "file
newname" in the command line window just fine.
:new<CR>
q:
afile new_name<CR>
--
Never under any circumstances take a sleeping pill
and a laxative on the same night.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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/d/optout.