Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Undefined variable: SignatureMarkText #109

Closed
wyne opened this issue Mar 10, 2016 · 14 comments
Closed

Undefined variable: SignatureMarkText #109

wyne opened this issue Mar 10, 2016 · 14 comments
Assignees
Labels

Comments

@wyne
Copy link

wyne commented Mar 10, 2016

Just installed fresh. Whenever I try to set a mark, I get this error:

E121: Undefined variable: SignatureMarkerText
E15: Invalid expression: SignatureMarkerText
Error detected while processing function signature#sign#Refresh..signature#sign#Place..<SNR>117_RefreshLine..<SNR>117_EvaluateHL:
line    2:
E121: Undefined variable: SignatureMarkText
E15: Invalid expression: SignatureMarkText
48;5;235mPress ENTER or type command to continue
@kshenoy
Copy link
Owner

kshenoy commented Mar 10, 2016

Hmm, this doesn't make sense. Did you put anything in your vimrc to get this working?

Can you start vim using the following command gvim -N -u <(echo 'set rtp+=~/.vim/bundle/vim-signature/') -U NONE and see if you still get the error?

Can you point me to your vimrc?

@wyne
Copy link
Author

wyne commented Mar 10, 2016

Hm, the error doesn't happen when i use that command. Maybe some other plugin I have installed is interfering.

I'm using neovim and my config is here:
https://github.com/wyne/dotfiles/blob/master/vim/.nvimrc

@kshenoy
Copy link
Owner

kshenoy commented Mar 10, 2016

Your rc file doesn't have any Signature related stuff in it. So I can't comment on it.

The reason I say it's weird is because I don't use variables named SignatureMarkText or SignatureMarkerText.

If you can figure out if it's due to interaction with some other plugin and which plugin it is it'd be a great help

@wyne
Copy link
Author

wyne commented Mar 10, 2016

Oh I see. That's helpful. Sorry, I just assumed it was vim-signature. I'll take a look and report back. Thanks.

@wyne
Copy link
Author

wyne commented Mar 10, 2016

Oh, looks like the morhetz/gruvbox and/or mhinz/vim-signify is causing the issue. Sorry for the false alarm and hanks for the quick response!

@wyne wyne closed this as completed Mar 10, 2016
@wyne
Copy link
Author

wyne commented Mar 10, 2016

Related: morhetz/gruvbox#38

@kshenoy
Copy link
Owner

kshenoy commented Mar 11, 2016

Umm, I'm not sure how Gruvbox is at fault here. Their code looks fine. Let me dig deeper.

Can you tell me if you get the error by starting vim like this:

gvim -N -U NONE -u <(cat << VIMRC
filetype plugin indent on
set rtp+=~/.vim/bundle/vim-signature
set rtp+=~/.vim/bundle/gruvbox
colorscheme gruvbox
VIMRC)

@wyne
Copy link
Author

wyne commented Mar 11, 2016

Running like this:

nvim -N -U NONE -u <(echo '
filetype plugin indent on
set rtp+=~/.config/nvim/bundle/vim-signature
set rtp+=~/.config/nvim/bundle/gruvbox
colorscheme gruvbox')

And as soon as it open, I do ma to set a mark:

line   22:
W18: Invalid character in group name
Press ENTER or type command to continue

@kshenoy
Copy link
Owner

kshenoy commented Mar 11, 2016

Can you try updating to the latest version and trying again? I put in some fixes that I think could be related to your issue.

@wyne
Copy link
Author

wyne commented Mar 11, 2016

vim-signature: 47ceaf9
gruvbox: 91bae6876031ececf151cc4f28aa5fb8c93681e4

Running with just gruvbox and vim-signature enabled, it's working fine now. Progress!

Though when I use my full vimrc, I get this error when doing ma on a new buffer:

E116: Invalid arguments for function has_key(b:sy.internal, a:lnum)
E15: Invalid expression: has_key(b:sy.internal, a:lnum)
Press ENTER or type command to continue

I'm not very familiar with how to debug these things, other than turning off other plugins.

@wyne
Copy link
Author

wyne commented Mar 11, 2016

Everything is working fine on existing files as opposed to new buffers, though. Not sure if that's meaningful or not.

@kshenoy
Copy link
Owner

kshenoy commented Mar 11, 2016

Can you please paste the contents of your full vimrc? The previous paste did not have signature install line or any signature related settings.

@kshenoy
Copy link
Owner

kshenoy commented Mar 11, 2016

Ok, I think I figured out what's wrong. Please try now.

@kshenoy kshenoy added the bug label Mar 11, 2016
@kshenoy kshenoy self-assigned this Mar 11, 2016
@wyne
Copy link
Author

wyne commented Mar 11, 2016

Updated to 17809de and no errors.

Thanks so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants