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

Popup alignment in php-mode inexplicably broken for me. #85

Open
aaronbieber opened this issue Feb 2, 2015 · 10 comments
Open

Popup alignment in php-mode inexplicably broken for me. #85

aaronbieber opened this issue Feb 2, 2015 · 10 comments
Labels

Comments

@aaronbieber
Copy link

I'm having the strangest problem all of a sudden with alignment of popup menus in auto-complete when using php-mode. This is what it looks like:

image

To try to diagnose whether this was just an issue with my config, I tried:

  1. Rolling back my .emacs by several weeks (it's in git, of course).
  2. Deleting my entire ~/.emacs.d/elpa directory and re-downloading/re-compiling all packages.

Neither of these helped. This problem doesn't seem to affect text-mode or lisp-interaction-mode, though, as shown here:

image

image

I've also opened an issue with php-mode, but they haven't been able to reproduce it. I have attempted to debug what is going on in popup.el, but admittedly my Lisp isn't very strong and I can't figure out how the placement of the left edge of the popup is computed.

Any help or direction on how to figure this out would be greatly appreciated.

@aaronbieber
Copy link
Author

I discovered that this behavior only happens when fci-mode is turned on, which leads me to believe that it is directly related to that package, and probably not a popup.el issue.

I am going to leave this open for now until someone from this project takes a peek at it and maybe helps to confirm this for me.

@m2ym m2ym added the bug label Feb 5, 2015
@kostafey
Copy link
Contributor

kostafey commented Apr 1, 2015

@aaronbieber, looks like posn-at-point problem. To verify this you can try popup-el version previous to this commit.

@diasjorge
Copy link

I have the same problem with the python-mode. I'm not using any proportional font so it's not related to some other bug reports.
I'm using el-get and I tried with different version of this mode, and I found that if I checkout tag v0.5.2 I don't have this problem but with v0.5.3 I do have it, so it must be a regression between those 2 releases

diasjorge added a commit to diasjorge/emacs-files that referenced this issue Nov 26, 2015
  * Version 0.5.3 has a bug with some modes
  * auto-complete/popup-el#85
@diasjorge
Copy link

After some more investigation I found that this is the commit that caused the problem:
f06712a

@syohex
Copy link
Contributor

syohex commented Nov 28, 2015

Could you show us minimum configuration for reproducing this issue ?

@diasjorge
Copy link

@syohex I found this minimum configuration. https://gist.github.com/diasjorge/4b6217ec577ce4c1b1f7
It appears to be an interaction between fci-mode and popup-el. It actually breaks in all modes I tested but I only had fci-mode activated with python-mode. I also found this bug which appears similar company-mode/company-mode#180

I really don't understand the code you made to deal with transparent overlays or something like that to say more but seems related.

@diasjorge
Copy link

I see there's this bug open for a long time alpaker/fill-column-indicator#21

@yilihong
Copy link

yilihong commented Aug 23, 2016

I am having this issue as well... anyone has a good solution? This is a popup for a English -> Chinese dictionary.

Did you eventually solve it? @aaronbieber

screenshot 2016-08-22 18 24 13

@syohex
Copy link
Contributor

syohex commented Aug 23, 2016

I suppose your issue is different from this, because it looks you use non monospaced font. It is difficult to support such fonts.

@yilihong
Copy link

Actually I do use mono spaced font. The English is "Hack", Chinese is also mono spaced. Don't know what's going on there...

On Aug 23, 2016, at 3:27 PM, Syohei YOSHIDA <[email protected]mailto:[email protected]> wrote:

I suppose your issue is different from this, because it looks you use non monospaced font. It is difficult to support such fonts.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com//issues/85#issuecomment-241900214, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALDt-jxNRrsguAXuzl9LGhmv33sxLQTiks5qi3PFgaJpZM4DagJh.

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

6 participants