Re: Question: Any reason why ":file" is disallowed in the cmdline window?

Good tips. Thank you! I indeed use older versions of Vim without `getwininfo()` on disparate machines. So, keeping this function is necessary at the moment. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

2018-05-24 0:53 GMT+03:00 Jason Franklin : > The first instance makes sense. After all, no one would want to change the > file name in the command line window. > > The second instance means that I can't run :file in the ftplugin for the "qf" > file type. I was

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

The first instance makes sense. After all, no one would want to change the file name in the command line window. The second instance means that I can't run :file in the ftplugin for the "qf" file type. I was previously doing this in my own "ftplugin/qf.vim" script to get the type of list I was

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

2018-05-24 0:33 GMT+03:00 Bram Moolenaar : > > Jason Franklin wrote: > >> To replicate with the cmdline window: >> >> vim -u NONE >> q: >> :file > > Well, what do you expect to happen? I would expect it to have same output as ``, though… > >> To replicate with the

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

Jason Franklin wrote: > To replicate with the cmdline window: > > vim -u NONE > q: > :file Well, what do you expect to happen? > To replicate with the quickfix window: > > vim -u NONE > :autocmd FileType qf file > :copen What's the use of :file here? > In both of these cases,

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

To replicate with the cmdline window: vim -u NONE q: :file To replicate with the quickfix window: vim -u NONE :autocmd FileType qf file :copen In both of these cases, ":file" fails. This is more what I was talking about. -- -- You received this message from the "vim_dev"

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

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. > >

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

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

Re: Question: Any reason why ":file" is disallowed in the cmdline window?

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

Question: Any reason why ":file" is disallowed in the cmdline window?

In the command index table, the ":file" command doesn't have the CMDWIN flag. This means it can't be called in the cmdline window. Should this be the case? I know that ":file" has variations that let you change the name of the current buffer, but it doesn't switch buffers that I can tell. One