search

darlingm / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

quickfix list should not process modelines #245

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. open a quickfix list with the first entry having a string like "vim: foo"
2. vim tries to process "foo" as a modeline

What is the expected output? What do you see instead?

There's no reason for the quickfix list to recognize modelines.

What version of the product are you using? On what operating system?

7.4, linux/mac/windows.

Original issue reported on code.google.com by justi...@gmail.com on 3 Aug 2014 at 4:45

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Precise steps to reproduce:

:cexpr ['vim: foo']

Vim reports "E518: Unknown option: foo"

Original comment by justi...@gmail.com on 3 Aug 2014 at 4:48

GoogleCodeExporter commented 9 years ago 
I am sorry, but I don't see this problem. Running 
vim -u NONE -N -c 'cexpr ["vim: foo"]'
Doesn't report an error message.

Original comment by chrisbr...@googlemail.com on 4 Aug 2014 at 12:13

GoogleCodeExporter commented 9 years ago 
You're right, there's some extra step that is needed. I see this issue often, 
but somehow I can't reproduce it at all now. I will report once I find the 
cause.

Original comment by justi...@gmail.com on 4 Aug 2014 at 2:02

GoogleCodeExporter commented 9 years ago 
Closing as invalid. If you can reproduce the issue, feel free to open a new 
issue (or report at the vim-dev mailinglist) then.

Original comment by chrisbr...@googlemail.com on 2 Oct 2014 at 7:44

GoogleCodeExporter commented 9 years ago 
This might happen when some plugin calls `doautocmd`, e.g. fugitive does this 
for its `:Glog`:

    BufRead Auto commands for "*"
    cmd: call fugitive#detect(expand('<amatch>:p'))

(reported at https://github.com/tpope/vim-fugitive/issues/580)

Modelines currently get executed unconditionally in this case, but even with 
the patch to only do so when commands have been called 
(https://groups.google.com/d/msg/vim_dev/DidKMDAsppw/RHedJGM-G6EJ) this is an 
issue.

It's not really a Vim issue though - except if Vim would decide to skip 
modelines for &buftype != "".

Original comment by dhahler@gmail.com on 20 Nov 2014 at 8:38