-
Notifications
You must be signed in to change notification settings - Fork 95
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
posn-at-point returns unexpected list #86
Comments
Another disadvantage of using |
I'm also encountering this error a lot of times:
|
@robert-zaremba Could you tell us how to reproduce your issue ? |
@robert-zaremba, Im my case you should create popup menu after ^L char in TAGS buffer. |
UPD: Is seems, it's hard to reproduce it any time. I'll try to find permanent reproduction steps. The last case here. UPD2: full repro seps:
(package-initialize)
(with-eval-after-load "popup-el")
(require 'popup)
(with-eval-after-load "fill-column-indicator")
(with-eval-after-load "clojure-mode")
(require 'fill-column-indicator)
(setq-default fill-column 80)
(setq-default fci-rule-column fill-column)
(setq fci-rule-width 1)
(define-globalized-minor-mode global-fci-mode fci-mode (lambda () (fci-mode 1)))
(global-fci-mode 1)
(global-linum-mode)
(set-face-font 'default "FiraMono-12.5:antialias=subpixel")
However, I'm afraid the result depends on your screen resolution and font size. Reproduction file example: https://github.com/kostafey/clucy/blob/master/src/clucy/positions_searcher.clj Trace:
|
In common cases
(posn-at-point)
returns structure like:(#<window 12 on TAGS<idid>> 90 (0 . 100) 0 nil 90 (0 . 5) nil (0 . 0) (10 . 20))
In rare cases
(posn-at-point)
returns:(#<frame : 0x1149ad8> nil (0 . 0) 0)
E.g. after
^L
char inTAGS
buffers.This leads to error on
popup-create
call:The early used
(popup-current-physical-column)
(see: kenbeese@c02ec73#diff-99b97c0478ea73bf04732050d7160dc4L539)don't have such problems.
Is it possible to return previous
(popup-current-physical-column)
usage or any other solutions to get current point position correctly in all cases?The text was updated successfully, but these errors were encountered: