comments hard to read when highlighted about vim HOT 10 CLOSED

I believe we've seen this before in various forms...

For example, it's mentioned in #37, which was supposedly closed by #62

However, I agree it still obscures comments. My one thought is that perhaps we shouldn't be reading comments when visually-selecting them? But still, anything we can do to make this a non-issue would be good.

@bricerebsamen do you have any suggestions on what might make a good replacement color for the DraculaSelection highlight color?

from vim.

we shouldn't be reading comments when visually-selecting them

sure but that's still a problem when editing the comments

from vim.

Agreed; that's why I'm asking for suggestions for a fix and recommending we fix it

from vim.

can you suggest a way for me to experiment? i.e. some vimrc line like let g:DraculaSelection = #rrggbb with the current color value. I can try to tweak and propose a new value.

from vim.

also maybe the proper tweak is to change the comment color to a slightly lighter value. same question: how would I experiment with that?

from vim.

DraculaSelection is defined here.

The selection value referenced above comes from here and is a list of

[ '#rrggbb' , closest_256-color_equivalent ]

Comment would be changed by experimenting with DraculaComment in that same file.

You'd most likely want to play around with a local copy of the repo and tweak the values in the colors file. You could edit it directly in your ~/.vim directory (idk your setup), or clone it fresh and start tweaking. Just make sure if you that you point your runtimepath over to the right copy so you can use that.

If you don't want to go to all that, you could probably try this in a vim session, but the above is more surefire.

:hi DraculaSelection [key]=[arg] " see :help :hi

from vim.

If I'm able to interject here 3 days later, I'd much rather see this discussed and changed here before doing anything drastic in this repo.

If there is agreement that this is a problem, the change should happen at the spec level, not at the implementation level.

At the end of the day, decisions like this should be left to @zenorocha

from vim.

I got the same problem too!
How did you fix this? @bricerebsamen

from vim.

Hitting this as well.

from vim.

Closing this until we get resolution on dracula/dracula-theme#318

from vim.