Comment #2 on issue 245 by justi...@gmail.com: quickfix list should not
process modelines
http://code.google.com/p/vim/issues/detail?id=245
Precise steps to reproduce:
:cexpr ['vim: foo']
Vim reports "E518: Unknown option: foo"
--
You received this message because this project is configure
Comment #1 on issue 245 by justi...@gmail.com: quickfix list should not
process modelines
http://code.google.com/p/vim/issues/detail?id=245
Precise steps to reproduce:
:expr ['vim: foo']
Vim reports "E518: Unknown option: foo"
--
You received this message because this project is configured
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 245 by justi...@gmail.com: quickfix list should not process
modelines
http://code.google.com/p/vim/issues/detail?id=245
What steps will reproduce the problem?
1. open a quickfix list with the first entry having a string lik
Comment #1 on issue 244 by brammool...@gmail.com: Patch for
/runtime/syntax/c.vim
http://code.google.com/p/vim/issues/detail?id=244
include_next is a GCC extension, it's not part of a C standard.
It should only be accepted when the user has indicated GCC extensions are
supported.
The gene
On 03/08/14 07:58, Paul Moore wrote:
[...]
Thanks for the explanation, but with all due respect, it doesn't seem
unreasonable to me for a user to expect that if they specify a
commonly-used monospace font like Consolas, Lucida Console, or even
Courier New, they should get behaviour that is simil
On 3 August 2014 06:58, Paul Moore wrote:
> not a "no such character" box, but a usable representation. Having to
> set a series of options that require a deep understanding of character
> sets and how fonts work should not be needed just to see the contents
> of a file to the level of clarity tha
