all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 23809@debbugs.gnu.org, vilanova@ac.upc.edu
Subject: bug#23809: 24.5; Positive argument to 'posn-at-point' throws erros as being negative
Date: Wed, 22 Jun 2016 18:06:56 +0300	[thread overview]
Message-ID: <8360t15kkv.fsf@gnu.org> (raw)
In-Reply-To: <576A2BE4.4070504@gmx.at> (message from martin rudalics on Wed, 22 Jun 2016 08:10:44 +0200)

> Date: Wed, 22 Jun 2016 08:10:44 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: vilanova@ac.upc.edu, 23809@debbugs.gnu.org
> 
>  > I don't like sweeping problems under the carpet.  We should understand
>  > how come we get negative pixel coordinates in these cases, it's most
>  > likely some bug in pos_visible_p or somesuch.
> 
> A ‘condition-case’ would fix the problem on the release branch and give
> you all the time to find the real cause.

the problem doesn't seem grave enough to rush with a solution.

> Also, unless we guard against ‘posn-at-point’ ever returning a
> negative y-value, there's no guarantee that finding the cause of the
> present problem will fix this issue once and for all.

We will cross that bridge when we get to it.

Thanks.





  reply	other threads:[~2016-06-22 15:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 16:30 bug#23809: 24.5; Positive argument to 'posn-at-point' throws erros as being negative Lluís Vilanova
2016-06-20 20:12 ` Eli Zaretskii
2016-06-21 13:07   ` martin rudalics
2016-06-21 15:15     ` Eli Zaretskii
2016-06-22  6:10       ` martin rudalics
2016-06-22 15:06         ` Eli Zaretskii [this message]
2016-06-21 13:17   ` Lluís Vilanova
2016-07-09 11:44     ` Eli Zaretskii
2016-07-11 10:23       ` Lluís Vilanova
2016-07-11 14:51         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8360t15kkv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23809@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    --cc=vilanova@ac.upc.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.