Hi,

On Thu, Jul 7, 2016 at 7:31 AM, Yegappan Lakshmanan <[email protected]> wrote:
> Hi,
>
> On Thu, Jul 7, 2016 at 1:09 AM, LCD 47 <[email protected]> wrote:
>> On 6 July 2016, Yegappan Lakshmanan <[email protected]> wrote:
>>> Hi,
>>>
>>> On Wed, Jul 6, 2016 at 2:18 PM, Daniel Hahler <[email protected]>
>>> wrote:
>>> >
>>> > set buftype=nofile
>>> > set noequalalways
>>> > call setqflist([{'lnum': 1, 'bufnr': 1, 'col': 0, 'valid': 1, 'vcol': 0,
>>> 'nr': 0, 'type': 'E', 'pattern': '', 'text': 'msg'}])
>>> > copen
>>> > resize 1
>>> > % vim -u minimal.vim
>>> >
>>> > Now going to the quickfix list (C-w j) and pressing Enter will
>>> > result in "E36: Not enough room".  This happens because the "nofile"
>>> > buffer will not be re-used to display the error,
>>> >
>>>
>>> Yes. This is by design.
>>
>>     Any particular reason why your designs tend to break things that
>> worked fine for 10+ years?  Just wondering.
>>
>
> This is the behavior of Vim for more than 10 years or so. I am able to
> reproduce this behavior even in vim 7.0. The recent changes to quickfix
> didn't change this behavior.
>
> Can you describe the quickfix functionality that was broken/changed by
> the recent changes?
>

BTW, the majority of the recent changes related to the quickfix/location list
feature are for adding unit tests. When I developed the location list feature
for Vim 7.0, majority of the quickfix features were not unit tested. The
recent changes addressed this and now around 85% of the quickfix and
location list code is under test.

Let us know if you see any of the recent changes break the previous
quickfix/location list functionality.

- Yegappan

>>
>>> When opening a file from the quickfix window, windows/buffers with
>>> 'buftype' set to "nofile" will be skipped. Many plugins set the
>>> 'buftype' to 'nofile' and use the buffer to display some content.
>>> Reusing that window for showing a selected file will impact the
>>> plugin.
>>>
>>> >
>>> > and when creating a new split apparently :1sp (or even :0sp?!) will
>>> > be used.
>>> >
>>>
>>> This is the expected behavior of the 'noequalalways' option.
>>

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

Raspunde prin e-mail lui