Colors not working. #1

kadamski · 2015-03-16T18:41:31Z

After searching, my result looks like this:

[1;31mdrivers/mmc/core/debugfs.c[0m[K
[1;30m 200 [0m[K-
[1;30m 201 [0m[K-   mmc_claim_host(host);
[1;30m 202 [0m[K-   mmc_set_clock(host, (unsigned int) val);
[1;30m 203 [0m[K:2: [32;40mmmc_release_host[0m[K(host);
[1;30m 204 [0m[K-
[1;30m 205 [0m[K-   return 0;
[1;30m 206 [0m[K-}

There are no colors and escape characters are seen so obviously something went wrong. Tested on both vim and gvim 7.4 on Linux.

The text was updated successfully, but these errors were encountered:

egradman · 2015-03-16T19:00:07Z

same on OSX console vim

gabesoft · 2015-03-16T21:51:12Z

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

egradman · 2015-03-16T21:56:02Z

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

On Mon, Mar 16, 2015 at 2:51 PM, Gabriel Adomnicai <notifications@github.com

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

gabesoft · 2015-03-17T01:01:05Z

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

egradman · 2015-03-17T02:32:34Z

they are

On Mon, Mar 16, 2015 at 6:01 PM, Gabriel Adomnicai <notifications@github.com

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

gabesoft · 2015-03-17T03:16:08Z

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 ?

kadamski · 2015-03-17T07:48:03Z

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.

egradman · 2015-03-17T16:46:49Z

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

On Tue, Mar 17, 2015 at 12:48 AM, Krzysztof A. Adamski <
notifications@github.com> 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

gabesoft · 2015-03-17T20:45:37Z

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

egradman · 2015-03-17T21:12:12Z

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 <notifications@github.com

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

egradman · 2015-03-17T21:14:49Z

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 eric@gradman.com 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 <
notifications@github.com> 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

egradman · 2015-03-17T21:48:34Z

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

gabesoft · 2015-03-17T22:43:26Z

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

gabesoft · 2015-03-17T22:50:25Z

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

egradman · 2015-03-17T23:16:06Z

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 <notifications@github.com

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

gabesoft · 2015-03-18T18:13:54Z

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.

egradman · 2015-03-18T18:59:02Z

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 <
notifications@github.com> 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

gabesoft · 2015-03-18T20:26:04Z

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

megalithic · 2015-03-21T01:12:10Z

👍 that mostly fixed it for me, thanks Gabriel.

gabesoft · 2015-03-28T22:43:59Z

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

gabesoft closed this as completed Mar 28, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Colors not working. #1

Colors not working. #1

kadamski commented Mar 16, 2015

egradman commented Mar 16, 2015

gabesoft commented Mar 16, 2015

egradman commented Mar 16, 2015

gabesoft commented Mar 17, 2015

egradman commented Mar 17, 2015

gabesoft commented Mar 17, 2015

kadamski commented Mar 17, 2015

egradman commented Mar 17, 2015

gabesoft commented Mar 17, 2015

egradman commented Mar 17, 2015

egradman commented Mar 17, 2015

egradman commented Mar 17, 2015

gabesoft commented Mar 17, 2015

gabesoft commented Mar 17, 2015

egradman commented Mar 17, 2015

gabesoft commented Mar 18, 2015

egradman commented Mar 18, 2015

gabesoft commented Mar 18, 2015

megalithic commented Mar 21, 2015

gabesoft commented Mar 28, 2015

Colors not working. #1

Colors not working. #1

Comments

kadamski commented Mar 16, 2015

egradman commented Mar 16, 2015

gabesoft commented Mar 16, 2015

egradman commented Mar 16, 2015

gabesoft commented Mar 17, 2015

egradman commented Mar 17, 2015

gabesoft commented Mar 17, 2015

kadamski commented Mar 17, 2015

egradman commented Mar 17, 2015

gabesoft commented Mar 17, 2015

egradman commented Mar 17, 2015

egradman commented Mar 17, 2015

egradman commented Mar 17, 2015

gabesoft commented Mar 17, 2015

gabesoft commented Mar 17, 2015

egradman commented Mar 17, 2015

gabesoft commented Mar 18, 2015

egradman commented Mar 18, 2015

gabesoft commented Mar 18, 2015

megalithic commented Mar 21, 2015

gabesoft commented Mar 28, 2015