Colors not working. about vim-ags HOT 20 CLOSED

same on OSX console vim

from vim-ags.

Looks like vim is not picking up the syntax highlighting. Can you verify that the search results window has filetype=agsv? Run set ft? in the search window

from vim-ags.

filetype=agsv <— that’s what I see.

On Mon, Mar 16, 2015 at 2:51 PM, Gabriel Adomnicai <[email protected]

wrote:

Looks like vim is not picking up the syntax highlighting. Can you verify
that the search results window has filetype=agsv? Run set ft? in the search
window

—
Reply to this email directly or view it on GitHub
#1 (comment).

Eric Gradman
CTO & Mad Inventor
P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/
TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS
Engineering Entertainment

Inventors | Developers | Performers

from vim-ags.

can you also check conceallevel and concealcursor, they should be 3 and nvic respectively in the search window

from vim-ags.

they are

On Mon, Mar 16, 2015 at 6:01 PM, Gabriel Adomnicai <[email protected]

wrote:

can you also check conceallevel and concealcursor, they should be 3 and
nvic respectively in the search window

—
Reply to this email directly or view it on GitHub
#1 (comment).

Eric Gradman
CTO & Mad Inventor
P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/
TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS
Engineering Entertainment

Inventors | Developers | Performers

from vim-ags.

One more thing to check is to make sure your vim is compiled with the conceal feature. When you run :version do you see +conceal ?

from vim-ags.

In my case filetype was not set to any value, setting it manually fixed the problem. And the reason for that was that I did not restart my vim after doing "BundleInstall". It seems that my vundle failed at inserting ftdetect rules after installation.

from vim-ags.

Yup, it has +conceal. I installed this plugin using pathogen, btw.

On Tue, Mar 17, 2015 at 12:48 AM, Krzysztof A. Adamski <
[email protected]> wrote:

In my case filetype was not set to any value, setting it manually fixed
the problem. And the reason for that was that I did not restart my vim
after doing "BundleInstall". It seems that my vundle failed at inserting
ftdetect rules after installation.

—
Reply to this email directly or view it on GitHub
#1 (comment).

Eric Gradman
CTO & Mad Inventor
P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/
TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS
Engineering Entertainment

Inventors | Developers | Performers

from vim-ags.

@egradman not sure why the syntax highlight is not picking up. Do you mind pasting a few lines from the search results window.

from vim-ags.

here’s a screenshot. The colors of the brackets are due to rainbow-parens
(come to think of it, perhaps if I disable that…)

https://www.dropbox.com/s/3ay46jywg7unz6x/Screenshot%202015-03-17%2014.11.07.png?dl=0

On Tue, Mar 17, 2015 at 1:45 PM, Gabriel Adomnicai <[email protected]

wrote:

@egradman https://github.com/egradman not sure why the syntax highlight
is not picking up. Do you mind pasting a few lines from the search results
window.

—
Reply to this email directly or view it on GitHub
#1 (comment).

Eric Gradman
CTO & Mad Inventor
P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/
TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS
Engineering Entertainment

Inventors | Developers | Performers

from vim-ags.

I just restarted vim with just your plugin and it works fine, so its
definitely a conflict with something else I’m running. I’ll figure out
which one it is and report back.

On Tue, Mar 17, 2015 at 2:11 PM, Eric Gradman [email protected] wrote:

here’s a screenshot. The colors of the brackets are due to rainbow-parens
(come to think of it, perhaps if I disable that…)

https://www.dropbox.com/s/3ay46jywg7unz6x/Screenshot%202015-03-17%2014.11.07.png?dl=0

On Tue, Mar 17, 2015 at 1:45 PM, Gabriel Adomnicai <
[email protected]> wrote:

@egradman https://github.com/egradman not sure why the syntax
highlight is not picking up. Do you mind pasting a few lines from the
search results window.

—
Reply to this email directly or view it on GitHub
#1 (comment).

Eric Gradman
CTO & Mad Inventor
P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/
TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS
Engineering Entertainment

Inventors | Developers | Performers

Eric Gradman
CTO & Mad Inventor
P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/
TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS
Engineering Entertainment

Inventors | Developers | Performers

from vim-ags.

Okay, it's definitely a conflict with https://github.com/luochen1990/rainbow

from vim-ags.

@egradman cool, that's good to know. I'll look at the rainbow plugin when I get home and see if there's anything I can do in vim-ags to eliminate the conflict.

from vim-ags.

Actually, I think it's just a matter of configuring the g:rainbow_conf option to disable rainbow parens for filetypes of agsv. Something like let g:rainbow_conf = { 'separately' : { 'agsv' : 0 } } should do the trick

from vim-ags.

so it would appear. this doesn’t seem to work however but I don’t think
it’s the fault of your plugin.

On Tue, Mar 17, 2015 at 3:50 PM, Gabriel Adomnicai <[email protected]

wrote:

Actually, I think it's just a matter of configuring the g:rainbow_conf
option to disable rainbow parens for filetypes of agsv. Something like let
g:rainbow_conf = { 'separately' : { 'agsv' : 0 } } should do the trick

—
Reply to this email directly or view it on GitHub
#1 (comment).

Eric Gradman
CTO & Mad Inventor
P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/
TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS
Engineering Entertainment

Inventors | Developers | Performers

from vim-ags.

I've tried the rainbow plugin and it seems to work properly. After I added this to my vimrc

let g:rainbow_conf = {
      \ 'separately' : { 'agsv' : 0 }
      \ }
let g:rainbow_active = 1

the search results picked up the correct syntax. You may need to restart vim for the changes to take effect.

from vim-ags.

I may have spoken too soon. I’m currently running vim with ONLY your
plugin and I’m seeing the same results...

What threw me off is that it seems to be dependent on my cwd when I run the
command.

Two fresh sessions of vim in two different directories (in two adjacent
iTerm windows): one renders correctly, one renders incorrectly.

On Wed, Mar 18, 2015 at 11:13 AM, Gabriel Adomnicai <
[email protected]> wrote:

I've tried the rainbow plugin and it seems to work properly. After I added
this to my vimrc

let g:rainbow_conf = {
\ 'separately' : { 'agsv' : 0 }
\ }
let g:rainbow_active = 1

the search results picked up the correct syntax. You may need to restart
vim for the changes to take effect.

—
Reply to this email directly or view it on GitHub
#1 (comment).

Eric Gradman
CTO & Mad Inventor
P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/
TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS
Engineering Entertainment

Inventors | Developers | Performers

from vim-ags.

What do the results look for the one that renders incorrectly?

from vim-ags.

👍 that mostly fixed it for me, thanks Gabriel.

from vim-ags.

I'll close this as it seems to be a configuration issue.

from vim-ags.