vscode-python VS nvim-ts-rainbow

Ah, Chrome and slow spinners.

Python tests were taking ages on VSCode due to an SVG spinner:

https://bugs.chromium.org/p/chromium/issues/detail?id=103626...

https://github.com/microsoft/vscode-python/issues/9216

It seems to be a problem caused by the new version of the Python extension. Here is a GitHub link for you to follow up.

For the python extension, please file your issue here: https://github.com/microsoft/vscode-python/issues

There seems to be a focus on feature velocity, and as the big parts start to stabilize (language server stuff, refactoring, extension framework, general UI/UX expectations), I hope we'll see some more attention paid to the default experience. But changing defaults in an ecosystem where users embrace configurability is tough, see the pythonPath fiasco, so I don't know the way forward. Core dev Brett Cannon seems to support the opinionated path for the VSCode Python experience going forward, so we'll see where that takes us.

I filed a GitHub report, you can always follow up.

Jedi said it had a fix on this post which links to this but isn't that just the Jedi source code showing fixes? The only reference I see in there is " Autocomplete inherited methods when overriding in child class ", but I just want it to autocomplete when typing a method from the parent class on a subclass instance.

If you still want to use python3.3.1 in vscode, you can submit a report on GitHub to consult the official staff.

It works fine on my machine after testing, can you provide your test code and show your personal settings(settings.json)? If you are convinced that this is a problem with python extensions, you can file a report on GitHub.

Does this help? Maybe you are opening the workspace at the wrong folder level?

Actually, it looks like it might be an issue with syntax highlighting ("Intellisense" in MS terminology) in Microsoft VS Code. Here is almost an identical post to mine in their forum.

for the past few days I have been working on a fork to the nvim-ts-rainbow plugin: nvim-ts-rainbow2. I am pretty much done, except for one small issue: finding out the level of a node relative to other container nodes. I know how to determine the level of a node in the tree (just keep counting up from 1 while going through the parents until I hit the root), but that is not what I need.

I noticed that it was abandoned when I was about to update my PR. The PR as it is up there is a mess, so I went through a major refactor and subsequently lost everything like an idiot.

The "look" you're looking for is given by a bunch of plugins: - OneDark.nvim as colorscheme - TS Rainbow for rainbow brackets - BarBar for bufferline - Nvim Devicons and NerdFonts to view file icons - NvimTree as a file manager - Indent Blankline to show indentation guides - CompetiTest with vertical split UI - Feline as statusline plugin. In the screenshot feline is configured with a custom theme. As you can see statusline is different for CompetiTest buffers: a different statusline can be configured for every different filetype using conditional_config.

For highlightning parentheses you could check out nvim-ts-rainbow

Consider using nvim-ts-rainbow to get rainbow parentheses.

To get changed colors for nested brackets, use nvim-ts-rainbow. I think the rest of the comments have you covered on getting colors up to snuff for you. To me it just looks like mismatched colors, not that anything is wrong

I'm happy to say I have fixed [the bug in nvim-ts-rainbow] that caused all JSX props to be highlighted](https://github.com/p00f/nvim-ts-rainbow/issues/118) in extended_mode instead of just highlighting the tag names. It was bugging me for a while when working on React components. Now, only the tag names and angle brackets in JSX elements are highlighted.

Lsp support is pretty good with Neovim, but obviously depends on what Lisp you use. I also like ts-rainbow a lot, but that's literally just visual fluff for brackets