On Fri, Aug 15, 2008 at 2:02 AM, Matt Wozniski wrote:
synIDattr() currently does not support the ability to read a 'guisp'
attribute from a highlight group, even though the underlying C
function it exposes does support it. I've attached a patch to update
the interface and docs to allow and
On 02/09/08 11:12, Matt Wozniski wrote:
On Fri, Aug 15, 2008 at 2:02 AM, Matt Wozniski wrote:
synIDattr() currently does not support the ability to read a 'guisp'
attribute from a highlight group, even though the underlying C
function it exposes does support it. I've attached a patch to
On Tue, Sep 2, 2008 at 6:42 AM, Tony Mechelynck wrote:
I'm seeing your message and I don't know the answer. Do you want a
similar message from everyone who doesn't know the answer?
Naturally not; your response was far more wasteful than my post
already, and not just because of wasting twice
Matt Wozniski wrote:
On Tue, Sep 2, 2008 at 6:42 AM, Tony Mechelynck wrote:
I'm seeing your message and I don't know the answer. Do you want a
similar message from everyone who doesn't know the answer?
Naturally not; your response was far more wasteful than my post
already, and
On 02/09/08 18:46, Charles Campbell wrote:
Matt Wozniski wrote:
On Tue, Sep 2, 2008 at 6:42 AM, Tony Mechelynck wrote:
I'm seeing your message and I don't know the answer. Do you want a
similar message from everyone who doesn't know the answer?
Naturally not; your response was far more
I was recently poking around a configure.in file when I noticed that vim
seemed to run afoul of highlighting it correctly, failing halfway
through. I traced the problem to a (copy-paste?) typo in
syntax/config.vim. Attached is a patch which fixes it.
--
Beware of bugs in the above code; I
On 03/09/08 06:11, Bill McCarthy wrote:
Hello Vim Developers,
I noticed a global variable that doesn't appear to be
intentionally set. The variable `cpo_save' undecorated and
outside a function is implicitly global.
Unfortunately `verbose let' does not reveal where it is set.
I found
