Arminius

Ha! Thanks for catching this. I'll look into it. (Unless someone else wants to supply a patch...)

I'm wondering if that's actually a bug in Python. Compare these two syntax trees: ``` >>> ast.parse("f'{a}'") Module( body=[ Expr( lineno=1, col_offset=0, value=JoinedStr( lineno=1, col_offset=0, values=[ FormattedValue( lineno=1, col_offset=0, value=Name(lineno=1,...

I filed a bug: https://bugs.python.org/issue35212

I'm currently experimenting with a parser based on tree-sitter instead of relying on Python's AST module. Once implemented, that would also eliminate bugs like this one.

> All the highlights are cleared when a syntax error detected. Highlights that have been applied should persist while a syntax error is present. Could you give a reproduction case...

Yep, these jumps should totally go into the jump list. Will look into it.

Thanks for reporting! This seems to be caused by a similar initialization bug as #10. Do you mind sharing which OS and neovim frontend you are using?

Odd, I'm using the exact same setup and don't experience the bug. - Can you reproduce it with a stripped-down `init.vim` and without any other plugins? (Or mind sharing your...

I couldn't reproduce the bug with your config. There seems to be some race condition during initialization. However, I modified initialization (83f56bfac9debd3c29ef7a9630b57e32d43e5f63) so that Semshi doesn't assume a particular event...

Thanks for your help resolving this bug! 1. You can set `let g:semshi#excluded_buffers = ['*']` to initially disable Semshi on all buffers. 2. I implemented `:Semshi toggle`. Does that enable...