-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Key not present in dictionary #41
Comments
Not sure why this is happening, it should always be added from the defaults here: gopher.vim/autoload/gopher/init.vim Line 79 in 8934106
Did you configure |
Thanks for the quick help! This has led me to investigate my let g:gopher_map = {'_nmap_prefix': '<Leader>', '_imap_prefix': '<C-g>' } in my This somehow works (e.g. this gets merged with the default values) when opening the first file, but overwrites everything when opening the second file... BTW: Using vim 8.2. Thanks again! Edit: it works when i set the specific keys in the dict instead of setting the whole dict. |
Hm, I can't reproduce it by adding that |
I'm able to "reproduce" it by adding the line: let g:gopher_map = {'_nmap_prefix': '<Leader>', '_imap_prefix': '<C-g>' } to my It works fine when using This can be fixed by either:
|
Ah right; checking for existence before (re-)defining it should work too I think:
I can look at making this more predictable; one thing I've been wanting to do is have buffer-local overrides for all the config settings, which requires changing the way this works anyway. |
Adding the above code snippet (with the adjusted assignment) doesn't work - it seems like the variable already exists when loading the syntax file. Nevertheless, with |
Cheers, glad the immediate issue is solved for you. I'll re-open this because it's something I do want to make sure gets fixed. You can unsubscribe if you don't any any further notifications 😅 |
Hi,
When opening a second
.go
file, I get the error message:This is caused by the code here:
gopher.vim/ftplugin/go.vim
Line 94 in 8934106
And the issue is fixed by uncommenting the specified line (obviously not a real solution).
Not quite sure if this is something related to my config / setup or an actual bug in the code. I'd be happy to provide any information necessary to debug this further.
Thanks!
The text was updated successfully, but these errors were encountered: