From: Dmitry Gutov <dgutov@yandex.ru>
To: Drew Adams <drew.adams@oracle.com>, 18493@debbugs.gnu.org
Subject: bug#18493: 24.3.93; posn-col-row should take text-scale-mode into account
Date: Thu, 18 Sep 2014 13:46:24 +0400 [thread overview]
Message-ID: <541AA9F0.2050409@yandex.ru> (raw)
In-Reply-To: <30fb9ae4-3781-4bc7-a1cf-45bf2a195929@default>
On 09/18/2014 05:56 AM, Drew Adams wrote:
> I don't understand why the value changing helps, instead of hurts,
> in that context. I would think that the column should not change
> just because the text is scaled. But I'm probably missing something.
Take a look at the implementation. The function takes pixel coordinates
and divides them by the frame-default character dimensions.
text-scale-mode is buffer-local, so it doesn't change the latter.
> It doesn't matter whether I do or don't. As a matter of fact, I do,
> but only a little bit - getting the column of a mouse click, using:
>
> (car (posn-col-row (event-start event)))
>
> And I guess that code must be broken wrt text scaling. I didn't
> realize that.
That was my point.
>> Is it aware of `posn-col-row' not being affected by text scale?
>
> I guess you mean *being* affected by it (?). IIUC, the return
> value depends on the text scale. Isn't that the bug you reported?
Indeed. By "not affected", I just meant that the implementation doesn't
take it into account.
next prev parent reply other threads:[~2014-09-18 9:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 22:03 bug#18493: 24.3.93; posn-col-row should take text-scale-mode into account Dmitry
2014-09-17 22:53 ` Drew Adams
2014-09-17 23:17 ` Dmitry Gutov
2014-09-18 1:56 ` Drew Adams
2014-09-18 9:46 ` Dmitry Gutov [this message]
2014-09-18 15:37 ` Drew Adams
2014-09-18 16:50 ` Eli Zaretskii
2014-09-18 14:59 ` Eli Zaretskii
2014-09-18 9:32 ` martin rudalics
2014-09-18 9:35 ` Dmitry Gutov
2014-09-18 14:58 ` Eli Zaretskii
2014-09-18 20:55 ` Dmitry Gutov
2014-09-19 1:05 ` Stefan Monnier
2014-09-19 1:07 ` Dmitry Gutov
2014-09-19 6:11 ` Eli Zaretskii
2014-09-19 11:17 ` Dmitry Gutov
2014-09-19 13:22 ` Eli Zaretskii
2014-09-19 18:08 ` Dmitry Gutov
2014-09-19 19:46 ` Eli Zaretskii
2014-09-22 3:59 ` Dmitry Gutov
2014-09-19 14:54 ` Stefan Monnier
2014-09-19 15:43 ` Eli Zaretskii
2014-09-19 17:38 ` Dmitry Gutov
2014-09-20 1:17 ` Stefan Monnier
2014-09-22 3:59 ` Dmitry Gutov
[not found] <<864mw529bx.fsf@yandex.ru>
[not found] ` <<38e6b538-3e76-472a-b371-2e74f9a14bf7@default>
[not found] ` <<541A1693.4090009@yandex.ru>
[not found] ` <<30fb9ae4-3781-4bc7-a1cf-45bf2a195929@default>
[not found] ` <<831tr92cuq.fsf@gnu.org>
2014-09-18 15:37 ` Drew Adams
2014-09-18 16:39 ` Eli Zaretskii
2014-09-19 1:00 ` Stefan Monnier
[not found] ` <<ebad225f-4bc4-426c-a135-8d1d15551fda@default>
[not found] ` <<83sijo2893.fsf@gnu.org>
2014-09-18 17:12 ` Drew Adams
2014-09-18 17:22 ` Eli Zaretskii
[not found] ` <<8338bp2cwf.fsf@gnu.org>
2014-09-18 15:52 ` Drew Adams
2014-09-18 17:00 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541AA9F0.2050409@yandex.ru \
--to=dgutov@yandex.ru \
--cc=18493@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).