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

broken display of show_call_signatures #302

Closed
escher9 opened this issue Aug 25, 2014 · 18 comments
Closed

broken display of show_call_signatures #302

escher9 opened this issue Aug 25, 2014 · 18 comments
Labels

Comments

@escher9
Copy link

escher9 commented Aug 25, 2014

hi, I saw similar issue opened few days ago, but can't find exact one again, sorry if opening duplicate one

screenshot_function
expect my vim to be above screenshot.. but

as following
fail

seems very near to the ideal but still trailing with ' ' (small quotes) and also flickering
notyet

while typing arguments, sometimes display is flickering(on off on off...)
ani
It seems that if above line is filled with some code, then flickering.

I'm sure that update to latest jedi (0.8.1_final0) and jedi-vim both.

my :ver is

ver

@davidhalter
Copy link
Owner

:colorscheme?

@escher9
Copy link
Author

escher9 commented Aug 25, 2014

colorscheme hybrid

@davidhalter
Copy link
Owner

It doesn't work with colorschemes.

@escher9
Copy link
Author

escher9 commented Aug 26, 2014

did you mean colorscheme matters?
(I've tried another {color schemes and font}, but that was no solution.
eg, colorscheme : default
font : fixedsys ... etc.
)

font name in uploaded screenshot is 'inconsolata for powerline'

@davidhalter
Copy link
Owner

I'm pretty sure that it's either your colorscheme (don't use any) or another syntax modification. Just disable everything that might do syntax modifications and you'll be fine. :)

@escher9
Copy link
Author

escher9 commented Aug 27, 2014

I understand, but how can I find one responsible for syntax modification?
if I thought that setting no other colorscheme results in ['default'] colorscheme...
I'm wrong?

@davidhalter
Copy link
Owner

No, you're right. But something else could do syntax modifications.

@escher9
Copy link
Author

escher9 commented Aug 27, 2014

Ok I'll try from bare minimum to find that cause.

@davidhalter
Copy link
Owner

Did you try?

Also I just updated jedi-vim's split character up there (the 0 that you see are actually complicated unicode characters.

@blueyed
Copy link
Collaborator

blueyed commented May 2, 2015

@davidhalter

It doesn't work with colorschemes.

Really? Works for me.

@escher9
There have been fixes to this feature a few weeks ago.
Can you retry it, please?

Apart from that I've just thought that maybe a setting like magic or verymagic etc might have an influence, because patterns would be treated differently.

@davidhalter
Copy link
Owner

It doesn't work with colorschemes.

Really? Works for me.

Yeah, I'm probably just saying that, because it didn't work a while ago. But since you improved to the syntax file, it could work better?!

@blueyed
Copy link
Collaborator

blueyed commented May 3, 2015

@davidhalter
Ah, that makes sense then.

@SamiAhola
Copy link

I could reproduce the on-off flickering effect with minimal configuration with latest Jedi and Jedi-Vim.

It seems that the code line that is masked by the signature is not analyzed anymore. For example:

  import logging
  logging.basicConfig(

here the signature of basicConfig masks the import statement causing the signature disappear when key is pressed. Now the import is no longer masked and the signature is shown again when a key is pressed. This causes the on-off effect. The problem can be fixed by introducing any line in between so that the import statement is not masked.

The effect is not limited to import statements, but any statement that affects the signature of the edited method. This can be seen in the example presented by escher9.

@blueyed
Copy link
Collaborator

blueyed commented Jun 10, 2015

@SamiAhola
Thanks for analysing.
I could imagine that temporarily disabling / ignoring the concealing would be required here. Although that might cause also some flickering then (always). But maybe it could be wrapped / get handled in a handler where Vim would not redraw anything.

@davidhalter
Copy link
Owner

@blueyed Since you've labeled it as a bug, what's the exact issue here?

@oblitum
Copy link

oblitum commented Jul 22, 2016

just to let the dots connected, cc #412

@blueyed
Copy link
Collaborator

blueyed commented Jan 8, 2017

Please try/test #652 and provide feedback there.
See https://help.github.com/articles/checking-out-pull-requests-locally/ for help on checking it out locally.

@blueyed blueyed closed this as completed Jul 28, 2018
@blueyed
Copy link
Collaborator

blueyed commented Jul 28, 2018

JFI: #652 is still alive.

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

5 participants