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

syntax enable problems #148

Open
mdlerch opened this issue Dec 19, 2014 · 1 comment
Open

syntax enable problems #148

mdlerch opened this issue Dec 19, 2014 · 1 comment

Comments

@mdlerch
Copy link

mdlerch commented Dec 19, 2014

The function r-plugin/functions.vim/FillRLibList() calls syntax enable and it is causing me some problems. At the least, my statusbar loses my specified coloring and my italicized comments (hi Comment cterm=italic) go back to regular font after :syntax enable. I have set both of these in my .vimrc. I'm not sure why this is happening because :help syn-enable says that my color settings should not be lost.

Any tips to fix this? By the way, this is happening both in neovim and regular vim.

@jalvesaq
Copy link

This means that I cannot use syntax enable. The solution that I have found was to set filetype after CursorMove event, but I now I think that BufEnter could have been better because it is called less frequently. I will change to BufEnter if we don't find a better solution. Perhaps we have to wait for neovim/neovim#901

jalvesaq added a commit to jalvesaq/Nvim-R that referenced this issue Apr 9, 2019
- No need of switching buffers for immediately updating the syntax
  highlighting of all buffers. This fix a very old issue:
  jcfaria/Vim-R-plugin#148

- No need of switching to the Object Browser buffer to update it.

- No need of switching to R Console buffer to move the cursor to its
  last line when R_auto_scroll = 1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants